From a707905a072a5bee25a138f65f29ba81ed609633 Mon Sep 17 00:00:00 2001 From: guangwu Date: Tue, 12 Sep 2023 17:12:39 +0800 Subject: [PATCH] fix: overridden typo (#1272) Signed-off-by: guoguangwu --- docs/traces.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/traces.md b/docs/traces.md index bca0abed46..2f24fd8db9 100644 --- a/docs/traces.md +++ b/docs/traces.md @@ -22,7 +22,7 @@ Sidecar use-case: ### Deployment By default the tracing is disabled and no sidecar container is being created during the k8gb deployment. To -enable the tracing, one has to set the `tracing.enabled=true` in Helm Chart. This will create the sidecar container for k8gb deployment, tweaks couple of env vars there. It will create the [configmap](https://github.com/k8gb-io/k8gb/blob/master/chart/k8gb/templates/otel/otel-config.yaml) for OTEL sidecar. This configuration of OTEL collector can be overriden by `tracing.otelConfig`. +enable the tracing, one has to set the `tracing.enabled=true` in Helm Chart. This will create the sidecar container for k8gb deployment, tweaks couple of env vars there. It will create the [configmap](https://github.com/k8gb-io/k8gb/blob/master/chart/k8gb/templates/otel/otel-config.yaml) for OTEL sidecar. This configuration of OTEL collector can be overridden by `tracing.otelConfig`. If you need something quickly up and running, make sure that `tracing.deployJaeger` is also set to `true`. In this scenario you will end up also with Jaeger deployed and service for it. To be able to access it one can continue with: