From c78cbdb35cb29f941f9d9f2ca9d30be853c4042a Mon Sep 17 00:00:00 2001 From: Yuri Shkuro Date: Thu, 14 Mar 2024 01:41:00 -0400 Subject: [PATCH] Fix HotROD instructions (#5273) ## Which problem is this PR solving? - The README was showing a command with the legacy OTEL_EXPORTER_JAEGER_ENDPOINT env var (using Jaeger format) ## Description of the changes - Change to use `OTEL_EXPORTER_OTLP_ENDPOINT` to match the `docker-compose` setup. Signed-off-by: Yuri Shkuro --- examples/hotrod/README.md | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/examples/hotrod/README.md b/examples/hotrod/README.md index b0dc9e8a305..190dd3dbd86 100644 --- a/examples/hotrod/README.md +++ b/examples/hotrod/README.md @@ -1,8 +1,6 @@ # Hot R.O.D. - Rides on Demand -This is a demo application that consists of several microservices and illustrates -the use of the OpenTelemetry API & SDK. It can be run standalone, but requires Jaeger backend -to view the traces. A tutorial / walkthrough is available: +This is a demo application that consists of several microservices and illustrates the use of the OpenTelemetry API & SDK. It can be run standalone, but requires Jaeger backend to view the traces. A tutorial / walkthrough is available: * as a blog post [Take Jaeger for a HotROD ride][hotrod-tutorial], * as a video [OpenShift Commons Briefing: Distributed Tracing with Jaeger & Prometheus on Kubernetes][hotrod-openshift]. @@ -54,7 +52,7 @@ An all-in-one Jaeger backend is packaged as a Docker container with in-memory st docker run \ --rm \ --name jaeger \ - -p6831:6831/udp \ + -p4318:4318 \ -p16686:16686 \ -p14268:14268 \ jaegertracing/all-in-one:latest @@ -75,7 +73,7 @@ go run ./examples/hotrod/main.go all docker run \ --rm \ --link jaeger \ - --env OTEL_EXPORTER_JAEGER_ENDPOINT=http://jaeger:14268/api/traces \ + --env OTEL_EXPORTER_OTLP_ENDPOINT=http://jaeger:4318 \ -p8080-8083:8080-8083 \ jaegertracing/example-hotrod:latest \ all