Skip to content

Commit

Permalink
Remove AWS Active Tracing span linking
Browse files Browse the repository at this point in the history
This aligns with the latest spec change:
open-telemetry/semantic-conventions#354

Providing the Lambda span's parent context should continue to be the responsibility of the global propagator.
  • Loading branch information
tylerbenson committed Mar 21, 2024
1 parent 0ccd4d3 commit eca064c
Show file tree
Hide file tree
Showing 4 changed files with 0 additions and 215 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -11,8 +11,6 @@ dependencies {

library("com.amazonaws:aws-lambda-java-core:1.0.0")

implementation("io.opentelemetry.contrib:opentelemetry-aws-xray-propagator")

// We do lightweight parsing of JSON to extract HTTP headers from requests for propagation.
// This will be commonly needed even for users that don't use events, but luckily it's not too big.
// Note that Lambda itself uses Jackson, but does not expose it to the function so we need to include
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,6 @@ public static AwsLambdaFunctionInstrumenter createInstrumenter(OpenTelemetry ope
openTelemetry,
"io.opentelemetry.aws-lambda-core-1.0",
AwsLambdaFunctionInstrumenterFactory::spanName)
.addSpanLinksExtractor(new AwsXrayEnvSpanLinksExtractor())
.addAttributesExtractor(new AwsLambdaFunctionAttributesExtractor())
.buildInstrumenter(SpanKindExtractor.alwaysServer()));
}
Expand Down

This file was deleted.

This file was deleted.

0 comments on commit eca064c

Please sign in to comment.