From d8baeeff219863412dcbe8d3556951abafef7518 Mon Sep 17 00:00:00 2001 From: Robb Kidd Date: Tue, 25 Apr 2023 19:32:25 -0400 Subject: [PATCH] fix a link to env config spec/docs Opted for the opentelemetry.io web site which might have more stable content locations than the github repo. --- docs/how-it-works.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/how-it-works.md b/docs/how-it-works.md index 959ce6154..5019ec1fd 100644 --- a/docs/how-it-works.md +++ b/docs/how-it-works.md @@ -6,7 +6,7 @@ We aim to bring the automatic instrumentation experience found in languages like - No code changes required - any Go application can be instrumented without modifying the source code. - Support wide range of Go applications - instrumentation is supported for Go version 1.12 and above. In addition, a common practice for Go applications is to shrink the binary size by stripping debug symbols via `go build -ldflags "-s -w"`. This instrumentation works for stripped binaries as well. -- Configuration is done via `OTEL_*` environment variables according to [OpenTelemetry Environment Variable Specification](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/sdk-environment-variables.md#general-sdk-configuration). +- Configuration is done via `OTEL_*` environment variables according to [OpenTelemetry Environment Variable Specification](https://opentelemetry.io/docs/reference/specification/sdk-environment-variables/#general-sdk-configuration). **In order to inject instrumentation into your process, set the `OTEL_TARGET_EXE` environment variable to the path of the target executable. This is not a part of the OTEL specification mentioned above.** - Instrumented libraries follow the [OpenTelemetry specification](https://github.com/open-telemetry/opentelemetry-specification) and semantic conventions to produce standard OpenTelemetry data.