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

Wrap the entire span lifecycle in SentryProducerInterceptor.onSend() in a single try-catch so instrumentation can never break the customer's Kafka send. The ProducerRecord is always returned regardless of any exception in Sentry code.

Previously, only header injection was guarded. Span creation (startChild), setData(), and finish() were unguarded — any exception from these would propagate and fail the customer's Kafka send per the ProducerInterceptor.onSend() contract.

The inner try-catch around injectHeaders is removed since the outer catch now covers it.

💡 Motivation and Context

Kafka's ProducerInterceptor.onSend() contract requires that interceptors not throw exceptions — any exception propagates and fails the send. Observability code must never cause customer message loss.

💚 How did you test it?

• All 8 existing SentryProducerInterceptorTest tests pass
• The change is purely defensive — wraps existing logic in try-catch without changing behavior

📝 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

Nothing.

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

#skip-changelog