Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
fix(alerts): Add logging to store data endpoint (#77662)
I'm trying to debug https://sentry.sentry.io/issues/5860348416/ where we're sending some `TimeSeriesPoint` values as `None`. The `dataset` is listed as `None` in the Sentry issue which means it should have gone into the else block in `format_historical_data` and in that case, there is no way we'd pass a `None` value. I added logging to try to figure out what's going on because I don't know how to store various performance data locally to be able to query snuba on it, and if there are no values the query only has timestamps, no other keys even with a None value. The `SnubaTSResult` has a `meta` key in it with usually something like "time" and then the snuba query aggregate name which would be used to populate the data if there were any, but unfortunately we can't use that directly because in the errors data for example, the snuba query aggregate is `count()` but the key in `SnubaTSResult` is `count`.
- Loading branch information