Inicio Explorar Axuda
Iniciar sesión
cecf
/
opentelemetry-java-instrumentation
7
0
Fork 0
Ficheiros Incidencias 0 Pull Requests 0 Wiki
Árbore: 97bc4a4fda
Ramas Etiquetas
opentelemetry-j...
/
instrumentation
/
aws-sdk
/
aws-sdk-2.2
/
library
Trask Stalnaker f1774cabe2 Update net semantic convention changes (#6268) %!s(int64=2) %!d(string=hai) anos
..
src f1774cabe2 Update net semantic convention changes (#6268) %!s(int64=2) %!d(string=hai) anos
README.md e01422736b Automatic AWS library instrumentor (#4607) %!s(int64=3) %!d(string=hai) anos
build.gradle.kts 14372adb68 Migrate Guava tests to Java (#5668) %!s(int64=3) %!d(string=hai) anos

README.md

AWS Java SDK v2 Instrumentation

Instrumentation for AWS Java SDK v2.

Usage

To instrument all AWS SDK clients include the opentelemetry-aws-sdk-2.2-autoconfigure submodule in your classpath.

To register instrumentation only on a specific 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.