You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add a TraceparentContextExtractor that parses standard W3C traceparent headers, enabling OTel trace continuity for customers not using X-Ray propagation.
November 2026 update
The Lambda Java runtime interface client added Context.w3c() in October. It exposes the W3C fields (traceparent, tracestate, and baggage) supplied in clientContext.w3c at invocation time. The default method returns an empty map, so getting those fields requires a runtime that populates them. Node.js, Python, and .NET added equivalent runtime APIs in October.
The Durable OTel plugins do not yet consume the new runtime APIs. For Java, the remaining work is to read traceparent from Context.w3c() and use it as the parent of the durable execution trace when present and valid. Whether to also support clientContext.custom.traceparent for compatibility with the existing JavaScript plugin path remains open.
One approach to export No-Arg OTel Plugin Constructor -
The ADOT Java agent supports customization via SPI (Service Provider Interface) extensions. An extension JAR can implement AutoConfigurationCustomizerProvider to inject a custom IdGenerator into the agent's TracerProvider at startup - before any spans are created. This lets our deterministic ID generator run inside the agent's single provider, eliminating the two-provider conflict that prevents wrapper compatibility today. The extension would be packaged as a separate Lambda layer and referenced via OTEL_JAVAAGENT_EXTENSIONS. With this approach, users would get the same setup simplicity as the JS/Python SDKs: one layer, one wrapper env var, and the plugin uses the global TracerProvider instead of creating its own. Auto-instrumented HTTP/AWS SDK spans would appear alongside durable execution spans in a single unified trace.
Activity
ayushiahjolia commentedon Jul 6, 2026
One approach to export No-Arg OTel Plugin Constructor -
The ADOT Java agent supports customization via SPI (Service Provider Interface) extensions. An extension JAR can implement AutoConfigurationCustomizerProvider to inject a custom IdGenerator into the agent's TracerProvider at startup - before any spans are created. This lets our deterministic ID generator run inside the agent's single provider, eliminating the two-provider conflict that prevents wrapper compatibility today. The extension would be packaged as a separate Lambda layer and referenced via OTEL_JAVAAGENT_EXTENSIONS. With this approach, users would get the same setup simplicity as the JS/Python SDKs: one layer, one wrapper env var, and the plugin uses the global TracerProvider instead of creating its own. Auto-instrumented HTTP/AWS SDK spans would appear alongside durable execution spans in a single unified trace.
ayushiahjolia commentedon Jul 30, 2026
moving no arg otel plugin support to #541
[-]OpenTelemetry Plugin Enhancements[/-][+]W3C Traceparent Support [/+]