From 5becdb4ddd33208d21cbf2293a5103ec799cc6d3 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Marcin=20Zi=C3=B3=C5=82kowski?= <62351083+MA3CIN@users.noreply.github.com> Date: Thu, 9 May 2024 10:16:10 +0200 Subject: [PATCH 1/2] Fix typo in troubleshooting.md MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Marcin Ziółkowski <62351083+MA3CIN@users.noreply.github.com> --- content/docs/next-release/troubleshooting.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/docs/next-release/troubleshooting.md b/content/docs/next-release/troubleshooting.md index 44b10ee7..90487924 100644 --- a/content/docs/next-release/troubleshooting.md +++ b/content/docs/next-release/troubleshooting.md @@ -12,7 +12,7 @@ If you are using the OpenTelemetry Collector as part of your pipeline, make sure Before everything else, make sure to confirm what sampling strategy is being used. For development purposes or for low-traffic scenarios, it is useful to sample every trace. In production, you may want to use lower rates. When diagnosing why spans are not being received by the backend, make sure to configure the SDK to _sample every trace_. Typically, the sampling strategy can be set via environment variables. -### OpenTelemtery SDKs +### OpenTelemetry SDKs If you are using OpenTelemetry SDKs, they should default to `parentbased_always_on` sampler, which is effectively sampling at 100%. It can be changed via `OTEL_TRACES_SAMPLER` environment variable ([see documentation](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/configuration/sdk-environment-variables.md)). From 7c1367e6e144c70e33cbf9da8344df4f5b9cef7e Mon Sep 17 00:00:00 2001 From: MA3CIN Date: Thu, 9 May 2024 10:19:49 +0200 Subject: [PATCH 2/2] fix Otel name type in troubleshooting.md Signed-off-by: MA3CIN --- content/docs/1.44/troubleshooting.md | 2 +- content/docs/1.45/troubleshooting.md | 2 +- content/docs/1.46/troubleshooting.md | 2 +- content/docs/1.47/troubleshooting.md | 2 +- content/docs/1.48/troubleshooting.md | 2 +- content/docs/1.49/troubleshooting.md | 2 +- content/docs/1.50/troubleshooting.md | 2 +- content/docs/1.51/troubleshooting.md | 2 +- content/docs/1.52/troubleshooting.md | 2 +- content/docs/1.53/troubleshooting.md | 2 +- content/docs/1.54/troubleshooting.md | 2 +- content/docs/1.55/troubleshooting.md | 2 +- content/docs/1.56/troubleshooting.md | 2 +- content/docs/1.57/troubleshooting.md | 2 +- 14 files changed, 14 insertions(+), 14 deletions(-) diff --git a/content/docs/1.44/troubleshooting.md b/content/docs/1.44/troubleshooting.md index 978e30bb..f6469851 100644 --- a/content/docs/1.44/troubleshooting.md +++ b/content/docs/1.44/troubleshooting.md @@ -10,7 +10,7 @@ Jaeger backend is itself a distributed system, composed of different components, Before everything else, make sure to confirm what sampling strategy is being used. For development purposes or for low-traffic scenarios, it is useful to sample every trace. In production, you may want to use lower rates. When diagnosing why spans are not being received by the backend, make sure to configure the SDK to _sample every trace_. Typically, the sampling strategy can be set via environment variables. -### OpenTelemtery SDKs +### OpenTelemetry SDKs If you are using OpenTelemetry SDKs, they should default to `parentbased_always_on` sampler, which is effectively sampling at 100%. It can be changed via `OTEL_TRACES_SAMPLER` environment variable ([see documentation](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/configuration/sdk-environment-variables.md)). diff --git a/content/docs/1.45/troubleshooting.md b/content/docs/1.45/troubleshooting.md index 978e30bb..f6469851 100644 --- a/content/docs/1.45/troubleshooting.md +++ b/content/docs/1.45/troubleshooting.md @@ -10,7 +10,7 @@ Jaeger backend is itself a distributed system, composed of different components, Before everything else, make sure to confirm what sampling strategy is being used. For development purposes or for low-traffic scenarios, it is useful to sample every trace. In production, you may want to use lower rates. When diagnosing why spans are not being received by the backend, make sure to configure the SDK to _sample every trace_. Typically, the sampling strategy can be set via environment variables. -### OpenTelemtery SDKs +### OpenTelemetry SDKs If you are using OpenTelemetry SDKs, they should default to `parentbased_always_on` sampler, which is effectively sampling at 100%. It can be changed via `OTEL_TRACES_SAMPLER` environment variable ([see documentation](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/configuration/sdk-environment-variables.md)). diff --git a/content/docs/1.46/troubleshooting.md b/content/docs/1.46/troubleshooting.md index 978e30bb..f6469851 100644 --- a/content/docs/1.46/troubleshooting.md +++ b/content/docs/1.46/troubleshooting.md @@ -10,7 +10,7 @@ Jaeger backend is itself a distributed system, composed of different components, Before everything else, make sure to confirm what sampling strategy is being used. For development purposes or for low-traffic scenarios, it is useful to sample every trace. In production, you may want to use lower rates. When diagnosing why spans are not being received by the backend, make sure to configure the SDK to _sample every trace_. Typically, the sampling strategy can be set via environment variables. -### OpenTelemtery SDKs +### OpenTelemetry SDKs If you are using OpenTelemetry SDKs, they should default to `parentbased_always_on` sampler, which is effectively sampling at 100%. It can be changed via `OTEL_TRACES_SAMPLER` environment variable ([see documentation](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/configuration/sdk-environment-variables.md)). diff --git a/content/docs/1.47/troubleshooting.md b/content/docs/1.47/troubleshooting.md index 44b10ee7..90487924 100644 --- a/content/docs/1.47/troubleshooting.md +++ b/content/docs/1.47/troubleshooting.md @@ -12,7 +12,7 @@ If you are using the OpenTelemetry Collector as part of your pipeline, make sure Before everything else, make sure to confirm what sampling strategy is being used. For development purposes or for low-traffic scenarios, it is useful to sample every trace. In production, you may want to use lower rates. When diagnosing why spans are not being received by the backend, make sure to configure the SDK to _sample every trace_. Typically, the sampling strategy can be set via environment variables. -### OpenTelemtery SDKs +### OpenTelemetry SDKs If you are using OpenTelemetry SDKs, they should default to `parentbased_always_on` sampler, which is effectively sampling at 100%. It can be changed via `OTEL_TRACES_SAMPLER` environment variable ([see documentation](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/configuration/sdk-environment-variables.md)). diff --git a/content/docs/1.48/troubleshooting.md b/content/docs/1.48/troubleshooting.md index 44b10ee7..90487924 100644 --- a/content/docs/1.48/troubleshooting.md +++ b/content/docs/1.48/troubleshooting.md @@ -12,7 +12,7 @@ If you are using the OpenTelemetry Collector as part of your pipeline, make sure Before everything else, make sure to confirm what sampling strategy is being used. For development purposes or for low-traffic scenarios, it is useful to sample every trace. In production, you may want to use lower rates. When diagnosing why spans are not being received by the backend, make sure to configure the SDK to _sample every trace_. Typically, the sampling strategy can be set via environment variables. -### OpenTelemtery SDKs +### OpenTelemetry SDKs If you are using OpenTelemetry SDKs, they should default to `parentbased_always_on` sampler, which is effectively sampling at 100%. It can be changed via `OTEL_TRACES_SAMPLER` environment variable ([see documentation](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/configuration/sdk-environment-variables.md)). diff --git a/content/docs/1.49/troubleshooting.md b/content/docs/1.49/troubleshooting.md index 44b10ee7..90487924 100644 --- a/content/docs/1.49/troubleshooting.md +++ b/content/docs/1.49/troubleshooting.md @@ -12,7 +12,7 @@ If you are using the OpenTelemetry Collector as part of your pipeline, make sure Before everything else, make sure to confirm what sampling strategy is being used. For development purposes or for low-traffic scenarios, it is useful to sample every trace. In production, you may want to use lower rates. When diagnosing why spans are not being received by the backend, make sure to configure the SDK to _sample every trace_. Typically, the sampling strategy can be set via environment variables. -### OpenTelemtery SDKs +### OpenTelemetry SDKs If you are using OpenTelemetry SDKs, they should default to `parentbased_always_on` sampler, which is effectively sampling at 100%. It can be changed via `OTEL_TRACES_SAMPLER` environment variable ([see documentation](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/configuration/sdk-environment-variables.md)). diff --git a/content/docs/1.50/troubleshooting.md b/content/docs/1.50/troubleshooting.md index 44b10ee7..90487924 100644 --- a/content/docs/1.50/troubleshooting.md +++ b/content/docs/1.50/troubleshooting.md @@ -12,7 +12,7 @@ If you are using the OpenTelemetry Collector as part of your pipeline, make sure Before everything else, make sure to confirm what sampling strategy is being used. For development purposes or for low-traffic scenarios, it is useful to sample every trace. In production, you may want to use lower rates. When diagnosing why spans are not being received by the backend, make sure to configure the SDK to _sample every trace_. Typically, the sampling strategy can be set via environment variables. -### OpenTelemtery SDKs +### OpenTelemetry SDKs If you are using OpenTelemetry SDKs, they should default to `parentbased_always_on` sampler, which is effectively sampling at 100%. It can be changed via `OTEL_TRACES_SAMPLER` environment variable ([see documentation](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/configuration/sdk-environment-variables.md)). diff --git a/content/docs/1.51/troubleshooting.md b/content/docs/1.51/troubleshooting.md index 44b10ee7..90487924 100644 --- a/content/docs/1.51/troubleshooting.md +++ b/content/docs/1.51/troubleshooting.md @@ -12,7 +12,7 @@ If you are using the OpenTelemetry Collector as part of your pipeline, make sure Before everything else, make sure to confirm what sampling strategy is being used. For development purposes or for low-traffic scenarios, it is useful to sample every trace. In production, you may want to use lower rates. When diagnosing why spans are not being received by the backend, make sure to configure the SDK to _sample every trace_. Typically, the sampling strategy can be set via environment variables. -### OpenTelemtery SDKs +### OpenTelemetry SDKs If you are using OpenTelemetry SDKs, they should default to `parentbased_always_on` sampler, which is effectively sampling at 100%. It can be changed via `OTEL_TRACES_SAMPLER` environment variable ([see documentation](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/configuration/sdk-environment-variables.md)). diff --git a/content/docs/1.52/troubleshooting.md b/content/docs/1.52/troubleshooting.md index 44b10ee7..90487924 100644 --- a/content/docs/1.52/troubleshooting.md +++ b/content/docs/1.52/troubleshooting.md @@ -12,7 +12,7 @@ If you are using the OpenTelemetry Collector as part of your pipeline, make sure Before everything else, make sure to confirm what sampling strategy is being used. For development purposes or for low-traffic scenarios, it is useful to sample every trace. In production, you may want to use lower rates. When diagnosing why spans are not being received by the backend, make sure to configure the SDK to _sample every trace_. Typically, the sampling strategy can be set via environment variables. -### OpenTelemtery SDKs +### OpenTelemetry SDKs If you are using OpenTelemetry SDKs, they should default to `parentbased_always_on` sampler, which is effectively sampling at 100%. It can be changed via `OTEL_TRACES_SAMPLER` environment variable ([see documentation](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/configuration/sdk-environment-variables.md)). diff --git a/content/docs/1.53/troubleshooting.md b/content/docs/1.53/troubleshooting.md index 44b10ee7..90487924 100644 --- a/content/docs/1.53/troubleshooting.md +++ b/content/docs/1.53/troubleshooting.md @@ -12,7 +12,7 @@ If you are using the OpenTelemetry Collector as part of your pipeline, make sure Before everything else, make sure to confirm what sampling strategy is being used. For development purposes or for low-traffic scenarios, it is useful to sample every trace. In production, you may want to use lower rates. When diagnosing why spans are not being received by the backend, make sure to configure the SDK to _sample every trace_. Typically, the sampling strategy can be set via environment variables. -### OpenTelemtery SDKs +### OpenTelemetry SDKs If you are using OpenTelemetry SDKs, they should default to `parentbased_always_on` sampler, which is effectively sampling at 100%. It can be changed via `OTEL_TRACES_SAMPLER` environment variable ([see documentation](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/configuration/sdk-environment-variables.md)). diff --git a/content/docs/1.54/troubleshooting.md b/content/docs/1.54/troubleshooting.md index 44b10ee7..90487924 100644 --- a/content/docs/1.54/troubleshooting.md +++ b/content/docs/1.54/troubleshooting.md @@ -12,7 +12,7 @@ If you are using the OpenTelemetry Collector as part of your pipeline, make sure Before everything else, make sure to confirm what sampling strategy is being used. For development purposes or for low-traffic scenarios, it is useful to sample every trace. In production, you may want to use lower rates. When diagnosing why spans are not being received by the backend, make sure to configure the SDK to _sample every trace_. Typically, the sampling strategy can be set via environment variables. -### OpenTelemtery SDKs +### OpenTelemetry SDKs If you are using OpenTelemetry SDKs, they should default to `parentbased_always_on` sampler, which is effectively sampling at 100%. It can be changed via `OTEL_TRACES_SAMPLER` environment variable ([see documentation](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/configuration/sdk-environment-variables.md)). diff --git a/content/docs/1.55/troubleshooting.md b/content/docs/1.55/troubleshooting.md index 44b10ee7..90487924 100644 --- a/content/docs/1.55/troubleshooting.md +++ b/content/docs/1.55/troubleshooting.md @@ -12,7 +12,7 @@ If you are using the OpenTelemetry Collector as part of your pipeline, make sure Before everything else, make sure to confirm what sampling strategy is being used. For development purposes or for low-traffic scenarios, it is useful to sample every trace. In production, you may want to use lower rates. When diagnosing why spans are not being received by the backend, make sure to configure the SDK to _sample every trace_. Typically, the sampling strategy can be set via environment variables. -### OpenTelemtery SDKs +### OpenTelemetry SDKs If you are using OpenTelemetry SDKs, they should default to `parentbased_always_on` sampler, which is effectively sampling at 100%. It can be changed via `OTEL_TRACES_SAMPLER` environment variable ([see documentation](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/configuration/sdk-environment-variables.md)). diff --git a/content/docs/1.56/troubleshooting.md b/content/docs/1.56/troubleshooting.md index 44b10ee7..90487924 100644 --- a/content/docs/1.56/troubleshooting.md +++ b/content/docs/1.56/troubleshooting.md @@ -12,7 +12,7 @@ If you are using the OpenTelemetry Collector as part of your pipeline, make sure Before everything else, make sure to confirm what sampling strategy is being used. For development purposes or for low-traffic scenarios, it is useful to sample every trace. In production, you may want to use lower rates. When diagnosing why spans are not being received by the backend, make sure to configure the SDK to _sample every trace_. Typically, the sampling strategy can be set via environment variables. -### OpenTelemtery SDKs +### OpenTelemetry SDKs If you are using OpenTelemetry SDKs, they should default to `parentbased_always_on` sampler, which is effectively sampling at 100%. It can be changed via `OTEL_TRACES_SAMPLER` environment variable ([see documentation](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/configuration/sdk-environment-variables.md)). diff --git a/content/docs/1.57/troubleshooting.md b/content/docs/1.57/troubleshooting.md index 44b10ee7..90487924 100644 --- a/content/docs/1.57/troubleshooting.md +++ b/content/docs/1.57/troubleshooting.md @@ -12,7 +12,7 @@ If you are using the OpenTelemetry Collector as part of your pipeline, make sure Before everything else, make sure to confirm what sampling strategy is being used. For development purposes or for low-traffic scenarios, it is useful to sample every trace. In production, you may want to use lower rates. When diagnosing why spans are not being received by the backend, make sure to configure the SDK to _sample every trace_. Typically, the sampling strategy can be set via environment variables. -### OpenTelemtery SDKs +### OpenTelemetry SDKs If you are using OpenTelemetry SDKs, they should default to `parentbased_always_on` sampler, which is effectively sampling at 100%. It can be changed via `OTEL_TRACES_SAMPLER` environment variable ([see documentation](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/configuration/sdk-environment-variables.md)).