fix(spring-jakarta): [Queue Instrumentation 12] Add Kafka retry count attribute#5282
Merged
adinauer merged 1 commit intofeat/queue-instrumentationfrom Apr 29, 2026
Conversation
… attribute Set messaging.message.retry.count on queue.process transactions when the Spring Kafka delivery attempt header is present. This keeps retry context on consumer traces without changing transaction lifecycle behavior. Co-Authored-By: Claude <noreply@anthropic.com>
Contributor
Semver Impact of This PR🟢 Patch (bug fixes) 📋 Changelog PreviewThis is how your changes will appear in the changelog. This PR will not appear in the changelog. 🤖 This preview updates automatically when you update the PR. |
This was referenced Apr 10, 2026
Merged
Sentry Build Distribution
|
Contributor
Performance metrics 🚀
|
This was referenced Apr 10, 2026
This was referenced Apr 20, 2026
Open
Open
This was referenced Apr 22, 2026
This was referenced Apr 22, 2026
Open
8 tasks
Base automatically changed from
fix/queue-instrumentation-producer-guard
to
feat/queue-instrumentation
April 29, 2026 13:33
8355a1e
into
feat/queue-instrumentation
102 of 109 checks passed
8 tasks
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.
PR Stack (Queue Instrumentation)
📜 Description
Set
messaging.message.retry.countonqueue.processtransactions when Spring Kafka provides the delivery attempt header. The retry count is derived asdeliveryAttempt - 1(attempt 1 → retry count 0).If the header is missing, malformed, or non-positive, no retry count attribute is added.
💡 Motivation and Context
Kafka retries currently create multiple
queue.processtransactions for the same record. Adding retry-count metadata makes attempts distinguishable in traces and aligns with Sentry conventions.💚 How did you test it?
./gradlew :sentry-spring-jakarta:test --tests='*SentryKafkaRecordInterceptorTest*'sets retry count from delivery attempt headerdoes not set retry count when delivery attempt header is missing📝 Checklist
sendDefaultPIIis enabled.🔮 Next steps
None.
#skip-changelog