Skip to content

W3C Traceparent Support  #479

Open
Open

Description

@ayushiahjolia

(Post-launch)

  1. W3C Traceparent Extraction Support
  • 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.

Activity

  1. moved this from Backlog to Ready in aws-durable-executionon Jun 20, 2026
  2. removed their assignment
    on Jun 30, 2026
  3. ayushiahjolia commented on Jul 6, 2026

    @ayushiahjolia
    ContributorAuthor

    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.

  4. added this to the 2.1 Jul 2026 milestone on Jul 7, 2026
  5. added
    projectIssues or pull requests that belong to an ongoing project
    on Jul 9, 2026
  6. ayushiahjolia commented on Jul 30, 2026

    @ayushiahjolia
    ContributorAuthor

    moving no arg otel plugin support to #541

  7. removed their assignment
    on Jul 30, 2026
  8. changed the title [-]OpenTelemetry Plugin Enhancements[/-] [+]W3C Traceparent Support [/+] on Aug 28, 2026
  9. removed this from the 2.2 Aug 2026 milestone on Aug 29, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    projectIssues or pull requests that belong to an ongoing project

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions