feat(micrometer): [Micrometer 1] Add active meters - #6085
Draft
adinauer wants to merge 4 commits into
Draft
adinauer wants to merge 4 commits into
adinauer wants to merge 4 commits into
Conversation
Copy link
Copy Markdown
Member
Sorry, something went wrong.
Add a framework-neutral Micrometer registry that forwards counters, timers, and distribution summaries through the existing Sentry metrics API while preserving local meter behavior. Register the new integration artifact and cover naming, units, filtering, scope resolution, and composite registry coexistence. Co-Authored-By: Claude <noreply@anthropic.com>
Copy link
Copy Markdown
Contributor
|
Sorry, something went wrong.
9 tasks
Copy link
Copy Markdown
📲 Install BuildsAndroid
|
Sorry, something went wrong.
This was referenced Sep 15, 2026
Use Micrometer's dot naming convention by default so exported metric names and tag keys match their instrumented forms. Keep the registry convention configurable for applications that need another format. Co-Authored-By: Claude <noreply@anthropic.com>
Express the registry's name-preservation contract directly instead of relying on Micrometer's dot alias for the identity convention. Co-Authored-By: Claude <noreply@anthropic.com>
Deactivate active meter wrappers when Micrometer removes them from the registry. Preserve local meter state while preventing stale handles from sending duplicate metrics after re-registration. Co-Authored-By: Claude <noreply@anthropic.com>
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
Reviewers
1 participant
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.
PR Stack (Micrometer)
📜 Description
Add the framework-neutral sentry-micrometer module and its public SentryMeterRegistry.
The registry forwards positive counter increments and individual timer and distribution-summary recordings through Sentry.metrics(). It remains a normal Micrometer registry for local reads, defaults to Micrometer's identity naming convention while remaining configurable, applies registry-local filters, converts tags and units to Sentry metric metadata, and coexists with other registries in a composite.
This PR also registers the artifact, SDK integration metadata, package documentation, and release metadata.
💡 Motivation and Context
Micrometer users currently need custom bridge code to send application metrics to Sentry. A dedicated registry lets applications add Sentry as another metrics destination without replacing Prometheus, Datadog, OTLP, or other registries.
This is the first PR in the Micrometer stack. Passive meter polling, FunctionTimer semantics, and Spring Boot auto-configuration follow separately.
💚 How did you test it?
Tests cover active meter forwarding, normal local reads, metadata conversion, filtering, dynamic Sentry scope resolution, failure isolation, lifecycle behavior, and composite-registry coexistence.
📝 Checklist
🔮 Next steps
Add passive gauge, long-task timer, and function-counter polling in the next stack PR.
#skip-changelog