feat(metrics): Add trace metrics behind an experiments flag#4898
Merged
sentrivana merged 15 commits intomasterfrom Oct 9, 2025
Merged
feat(metrics): Add trace metrics behind an experiments flag#4898sentrivana merged 15 commits intomasterfrom
sentrivana merged 15 commits intomasterfrom
Conversation
Similar to getsentry/sentry-javascript#17883, this allows the py sdk to send in new trace metric protocol items, although this code is experimental since the schema may still change. Most of this code has been copied from logs (eg. log batcher -> metrics batcher) in order to dogfood, once we're more sure of our approach we can refactor.
…ce trace metric is an internal dataset detail
sentrivana
added a commit
that referenced
this pull request
Oct 9, 2025
### Description Remove old metrics code to make way for #4898 Metrics was always an experimental feature and Sentry stopped accepting metrics a year ago. #### Issues <!-- * resolves: #1234 * resolves: LIN-1234 --> #### Reminders - Please add tests to validate your changes, and lint your code using `tox -e linters`. - Add GH Issue ID _&_ Linear ID (if applicable) - PR title should use [conventional commit](https://develop.sentry.dev/engineering-practices/commit-messages/#type) style (`feat:`, `fix:`, `ref:`, `meta:`) - For external contributors: [CONTRIBUTING.md](https://github.com/getsentry/sentry-python/blob/master/CONTRIBUTING.md), [Sentry SDK development docs](https://develop.sentry.dev/sdk/), [Discord community](https://discord.gg/Ww9hbqr)
sentrivana
reviewed
Oct 9, 2025
Contributor
sentrivana
left a comment
There was a problem hiding this comment.
Looking good overall, some minor things we should fix, see comments. Also happy to take over, lmk if you'd prefer that
One general note: We've removed the old metrics stuff in #4899, so the name "metrics" is up for grabs. Unless we specifically want to call this feature "trace metrics". Whatever we decide, we should pick one and stick with it throughout the PR.
Contributor
|
@k-fish I'll take care of the changes so that we can cut a release with this soon 🏃🏻 |
sentrivana
approved these changes
Oct 9, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Similar to getsentry/sentry-javascript#17883, this allows the py sdk to send in new trace metric protocol items, although this code is experimental since the schema may still change. Most of this code has been copied from logs (eg. log batcher -> metrics batcher) in order to dogfood, once we're more sure of our approach we can refactor.
Closes LOGS-367