Skip to content
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

feat(metric-meta): Add support for metric metadata #2751

Merged
merged 8 commits into from
Nov 27, 2023

Conversation

Dav1dde
Copy link
Member

@Dav1dde Dav1dde commented Nov 21, 2023

Implements metric_meta envelope item and storage in Redis.

Epic: getsentry/sentry#60260

@Dav1dde Dav1dde self-assigned this Nov 22, 2023
@Dav1dde Dav1dde force-pushed the feat/metric-metadata branch 2 times, most recently from b21cf98 to 605c257 Compare November 22, 2023 15:25
@Dav1dde Dav1dde marked this pull request as ready for review November 22, 2023 15:25
@Dav1dde Dav1dde requested a review from a team November 22, 2023 15:25
@Dav1dde Dav1dde force-pushed the feat/metric-metadata branch 3 times, most recently from a76c8f5 to 1db5de2 Compare November 22, 2023 15:34
@Dav1dde Dav1dde force-pushed the feat/metric-metadata branch 2 times, most recently from dafb35b to 258fdeb Compare November 23, 2023 16:48
@Dav1dde Dav1dde force-pushed the feat/metric-metadata branch 3 times, most recently from 59d2b60 to 5ef85c0 Compare November 24, 2023 11:22
@Dav1dde Dav1dde force-pushed the feat/metric-metadata branch 2 times, most recently from a48f878 to 91da0d1 Compare November 24, 2023 11:32
@Dav1dde Dav1dde force-pushed the feat/metric-metadata branch from 91da0d1 to 64aefb3 Compare November 24, 2023 11:33
@Dav1dde Dav1dde force-pushed the feat/metric-metadata branch from faa64da to 3e35438 Compare November 24, 2023 14:30
sthagen pushed a commit to sthagen/getsentry-sentry-python that referenced this pull request 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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants