-
-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Milestone] Metrics Meta Data #60260
Comments
This was referenced Nov 22, 2023
sthagen
pushed a commit
to sthagen/getsentry-sentry-python
that referenced
this issue
Nov 24, 2023
DDM wants to show code locations with metrics. Locations are semi-static information: they change infrequently, so they don't need to be reported with every data point. Sentry expects locations to be reported at least once per day. With backdating of metrics, the timestamp used to report the location is the metric bucket's timestamp rounded down to the start of the day (UTC timezone). The metrics aggregator keeps a cache of previously reported locations. When a location is seen for the first time on a day, it is added to a list of pending locations. On the next flush cycle, all pending locations are sent to Sentry in the same envelope as the metric buckets. See: getsentry/relay#2751 Epic: getsentry/sentry#60260 --------- Co-authored-by: Armin Ronacher <armin.ronacher@active-4.com> Co-authored-by: Anton Pirker <anton.pirker@sentry.io>
phacops
pushed a commit
to getsentry/relay
that referenced
this issue
Nov 27, 2023
Implements `metric_meta` envelope item and storage in Redis. Epic: getsentry/sentry#60260
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
DDM wants to show code locations with metrics. This is semi-static information, in that it changes infrequently between deploys, but doesn't need to be reported with every data point. The code locations should be shown in the DDM explorer.
Feature Set:
PoC
Goals:
Constraints:
Design Doc
Stage 1: PoC
Stage 2: Productionize for LA
Q1: GA Follow-up
The text was updated successfully, but these errors were encountered: