From c9f4cfc0d63cf90ccb811eb74fdfb456ca590142 Mon Sep 17 00:00:00 2001 From: MyMirelHub <15373565+MyMirelHub@users.noreply.github.com> Date: Wed, 22 Oct 2025 15:52:00 +0200 Subject: [PATCH 1/2] update Jaeger setup instructions for port conflict and background container Signed-off-by: MyMirelHub <15373565+MyMirelHub@users.noreply.github.com> --- .../open-telemetry-collector-jaeger.md | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/daprdocs/content/en/operations/observability/tracing/otel-collector/open-telemetry-collector-jaeger.md b/daprdocs/content/en/operations/observability/tracing/otel-collector/open-telemetry-collector-jaeger.md index fc1d91aca56..1bf9adb3bb8 100644 --- a/daprdocs/content/en/operations/observability/tracing/otel-collector/open-telemetry-collector-jaeger.md +++ b/daprdocs/content/en/operations/observability/tracing/otel-collector/open-telemetry-collector-jaeger.md @@ -17,8 +17,12 @@ Dapr supports writing traces using the OpenTelemetry (OTLP) protocol, and Jaeger The simplest way to start Jaeger is to run the pre-built, all-in-one Jaeger image published to DockerHub and expose the OTLP port: +> **Note:** Port 9411 is commonly used by Zipkin. If you have Zipkin running (starts by default when you run `dapr init`), stop the `dapr_zipkin` container first to avoid port conflicts: `docker stop dapr_zipkin` + + + ```bash -docker run --rm --name jaeger \ +docker run -d --rm --name jaeger \ -p 16686:16686 \ -p 4317:4317 \ -p 4318:4318 \ @@ -27,6 +31,12 @@ docker run --rm --name jaeger \ cr.jaegertracing.io/jaegertracing/jaeger:2.11.0 ``` +You can also view the logs the jaeger container using: + +```bash +docker logs jaeger +``` + Next, create the following `config.yaml` file locally: > **Note:** Because you are using the Open Telemetry protocol to talk to Jaeger, you need to fill out the `otel` section of the tracing configuration and set the `endpointAddress` to the address of the Jaeger container. From fb3321163f5e356a96830d45bf14b5a83ecb7405 Mon Sep 17 00:00:00 2001 From: MyMirelHub <15373565+MyMirelHub@users.noreply.github.com> Date: Wed, 22 Oct 2025 15:53:28 +0200 Subject: [PATCH 2/2] fix spacing Signed-off-by: MyMirelHub <15373565+MyMirelHub@users.noreply.github.com> --- .../tracing/otel-collector/open-telemetry-collector-jaeger.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/daprdocs/content/en/operations/observability/tracing/otel-collector/open-telemetry-collector-jaeger.md b/daprdocs/content/en/operations/observability/tracing/otel-collector/open-telemetry-collector-jaeger.md index 1bf9adb3bb8..ab3819ea8a5 100644 --- a/daprdocs/content/en/operations/observability/tracing/otel-collector/open-telemetry-collector-jaeger.md +++ b/daprdocs/content/en/operations/observability/tracing/otel-collector/open-telemetry-collector-jaeger.md @@ -19,8 +19,6 @@ The simplest way to start Jaeger is to run the pre-built, all-in-one Jaeger imag > **Note:** Port 9411 is commonly used by Zipkin. If you have Zipkin running (starts by default when you run `dapr init`), stop the `dapr_zipkin` container first to avoid port conflicts: `docker stop dapr_zipkin` - - ```bash docker run -d --rm --name jaeger \ -p 16686:16686 \