open-telemetry
/
opentelemetry-java-instrumentation
mirror of https://github.com/open-telemetry/opentelemetry-java-instrumentation.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
opentelemetry-java-instrume.../instrumentation/aws-sdk/aws-sdk-2.2/library
History
Mateusz Rzeszutek 15ed01d4fc
Change all instrumentation names to io.opentelemetry.{libName}-{libVersion} (#3411) 
* Change all instrumentation names to io.opentelemetry.{libName}-{libVersion}

* minumum supported version
 		2021-06-30 15:34:36 +02:00
..
src Change all instrumentation names to io.opentelemetry.{libName}-{libVersion} (#3411) 2021-06-30 15:34:36 +02:00
README.md Make sure AWS SDK spans suppress client spans all the time. (#1837) 2020-12-07 17:10:43 +09:00
build.gradle.kts Migrate instrumentation gradle files to kotlin (#3414) 2021-06-28 17:27:12 +09:00

README.md

AWS Java SDK v2 Instrumentation

Instrumentation for AWS Java SDK v2.

Usage

To register instrumentation on an SDK client, register the interceptor when creating it.

DynamoDbClient client = DynamoDbClient.builder()
  .overrideConfiguration(ClientOverrideConfiguration.builder()
    .addExecutionInterceptor(AwsSdk.newInterceptor()))
    .build())
  .build();

Trace propagation

The AWS SDK instrumentation currently only supports injecting the trace header into the request using the AWS Trace Header format. This format is the only format recognized by AWS managed services, and populating will allow propagating the trace through them. If this does not fulfill your use case, perhaps because you are using the same SDK with a different non-AWS managed service, let us know so we can provide configuration for this behavior.