fix(spring-jakarta): [Queue Instrumentation 12] Add Kafka retry count attribute

[adinauer]

PR Stack (Queue Instrumentation)

• feat(core): [Queue Instrumentation 1] Add enableQueueTracing option and messaging span data conventions #5250
• feat(samples): [Queue Instrumentation 2] Add Kafka to Spring Boot 3 sample app #5253
• feat(spring-jakarta): [Queue Instrumentation 3] Add Kafka producer instrumentation #5254
• feat(spring-jakarta): [Queue Instrumentation 4] Add Kafka consumer instrumentation #5255
• feat(spring-boot-jakarta): [Queue Instrumentation 5] Add Kafka queue auto-configuration #5259
• test(samples): [Queue Instrumentation 6] Add Kafka queue system tests #5260
• feat(samples): [Queue Instrumentation 7] Add Kafka to Spring Boot 3 OTel sample apps #5265
• fix(spring-boot-jakarta): [Queue Instrumentation 8] Disable Sentry Kafka spans when OTel is active #5274
• fix(spring-jakarta): [Queue Instrumentation 9] Clean up stale ThreadLocal context in Kafka consumer interceptor #5279
• fix(spring-jakarta): [Queue Instrumentation 10] Fork root scopes and skip when OTel is active in Kafka consumer #5280
• fix(spring-jakarta): [Queue Instrumentation 11] Guard entire span lifecycle in Kafka producer interceptor #5281
• fix(spring-jakarta): [Queue Instrumentation 12] Add Kafka retry count attribute #5282
• fix(spring-jakarta): [Queue Instrumentation 13] Align enqueue time with Python #5283

---

📜 Description

Set messaging.message.retry.count on queue.process transactions when Spring Kafka provides the delivery attempt header. The retry count is derived as deliveryAttempt - 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.process transactions for the same record. Adding retry-count metadata makes attempts distinguishable in traces and aligns with Sentry conventions.

💚 How did you test it?

• Ran ./gradlew :sentry-spring-jakarta:test --tests='*SentryKafkaRecordInterceptorTest*'
• Added tests:
  • sets retry count from delivery attempt header
  • does not set retry count when delivery attempt header is missing

📝 Checklist

• I added GH Issue ID & Linear ID
• I added tests to verify the changes.
• No new PII added or SDK only sends newly added PII if sendDefaultPII is enabled.
• I updated the docs if needed.
• I updated the wizard if needed.
• Review from the native team if needed.
• No breaking change or entry added to the changelog.
• No breaking change for hybrid SDKs or communicated to hybrid SDKs.

🔮 Next steps

None.

⚠️ Merge this PR using a merge commit (not squash). Only the collection branch is squash-merged into main.

#skip-changelog

[github-actions]

Semver Impact of This PR

🟢 Patch (bug fixes)

📋 Changelog Preview

This is how your changes will appear in the changelog.
Entries from this PR are highlighted with a left border (blockquote style).

---

This PR will not appear in the changelog.

---

_{🤖 This preview updates automatically when you update the PR.}

[sentry]

Sentry Build Distribution

App Name	App ID	Version	Configuration	Install Page
SDK Size	io.sentry.tests.size	8.37.1 (1)	release	Install Build

Configure sentry-android build distribution settings

[github-actions]

Performance metrics 🚀

	Plain	With Sentry	Diff
Startup time	316.72 ms	373.91 ms	57.19 ms
Size	0 B	0 B	0 B

Baseline results on branch: fix/queue-instrumentation-producer-guard

Startup times

Revision	Plain	With Sentry	Diff
8bb14c7	347.98 ms	413.21 ms	65.23 ms

App size

Revision	Plain	With Sentry	Diff
8bb14c7	0 B	0 B	0 B