You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
*Issue #, if available:*
*Description of changes:*
update resource link in README.md since it has moved to
[opentelemetry-java-contrib](https://github.com/open-telemetry/opentelemetry-java-contrib)
repository
By submitting this pull request, I confirm that my contribution is made
under the terms of the Apache 2.0 license.
Copy file name to clipboardExpand all lines: README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,7 +29,7 @@ This configuration includes being able to reconfigure the [IdsGenerator](https:/
29
29
which we need to support X-Ray compatible trace IDs. Because the SDK uses SPI, it is sufficient for
30
30
the custom implementation to be on the classpath to be recognized. The AWS distribution of the
31
31
OpenTelemetry Java Agent repackages the upstream agent by simply adding our SPI implementation for
32
-
reconfiguring the ID generator. In addition, it includes [AWS resource providers](https://github.com/open-telemetry/opentelemetry-java/tree/main/sdk-extensions/aws/src/main/java/io/opentelemetry/sdk/extension/aws/resource)
32
+
reconfiguring the ID generator. In addition, it includes [AWS resource providers](https://github.com/open-telemetry/opentelemetry-java-contrib/tree/main/aws-resources/src/main/java/io/opentelemetry/contrib/aws/resource)
33
33
by default, and it sets a system property to configure the agent to use multiple trace ID propagators,
0 commit comments