Skip to content

fix(otel): align service identity and Java ADOT initialization - #64

Draft
zhongkechen wants to merge 4 commits into
codex/continuous-otel-long-runningfrom
codex/align-otel-service-name
Draft

fix(otel): align service identity and Java ADOT initialization#64
zhongkechen wants to merge 4 commits into
codex/continuous-otel-long-runningfrom
codex/align-otel-service-name

Conversation

@zhongkechen

@zhongkechen zhongkechen commented Aug 4, 2026

Copy link
Copy Markdown
Contributor

Summary

  • standardize the deployed OpenTelemetry resource identity on durable-execution-conformance
  • make X-Ray declare PLUGIN_MODE_SERVICE_NAME and query spans with the capitalized deployed OTEL_PLUGIN_MODE, removing the separate discovery service-name option
  • initialize Java ADOT plugins through the Java-agent SPI and global tracer provider, exporting OTLP through the ADOT collector
  • package the Java plugin as /var/task/lib/otel-plugin-extension.jar and enable the ADOT wrapper in regular and long-running templates
  • retain the explicit tracer-provider builder for community OTLP endpoints and update workflows, documentation, and regression coverage

Testing

  • JAVA_SDK_VERSION=2.1.1-SNAPSHOT mvn -B clean package --file packages/aws-durable-execution-conformance-tests-otel/examples/java/pom.xml (3 tests)
  • hatch run test:all (339 tests)
  • hatch run types:check
  • hatch fmt --check
  • hatch run yaml:lint
  • sam build --template-file packages/aws-durable-execution-conformance-tests-otel/examples/java/template.yaml
  • sam validate --lint for both Java templates
  • git diff --check

Dependencies

@zhongkechen zhongkechen changed the title fix(otel): separate resource and discovery service names fix(otel): align service identity and Java ADOT initialization Aug 5, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant