From e338c10c6e6f59491cbbd50a936057bdc3d52199 Mon Sep 17 00:00:00 2001 From: Joe Heck Date: Mon, 1 Apr 2024 11:18:03 -0700 Subject: [PATCH] update the otel-config to match latest otel image Found the existing configuration wasn't working with the latest otel docker image, and in digging, found that `jaeger` is no longer a valid exporter for otel-collector. Since Jaeger has an OTLP collector itself now directly available, this updates the 'jaeger' exporter to use `otlp` instead. Kudos to https://stackoverflow.com/questions/77475771/error-when-running-otel-collector-with-jaeger-in-docker-containers, which helped me identify the fix --- Samples/Dinner/docker/collector-config.yaml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/Samples/Dinner/docker/collector-config.yaml b/Samples/Dinner/docker/collector-config.yaml index d07e13d..df239f5 100644 --- a/Samples/Dinner/docker/collector-config.yaml +++ b/Samples/Dinner/docker/collector-config.yaml @@ -8,8 +8,8 @@ exporters: logging: verbosity: detailed - jaeger: - endpoint: "jaeger:14250" + otlp: + endpoint: jaeger:4317 tls: insecure: true @@ -21,4 +21,4 @@ service: pipelines: traces: receivers: otlp - exporters: [logging, jaeger, zipkin] + exporters: [logging, otlp, zipkin]