Skip to content

Conversation

@network-charles
Copy link

@network-charles network-charles commented Nov 2, 2025

The PR addresses the following:

  • Clarifies how to visualize traces on Jaeger.
  • Added pauses using a commas and grammar articles where necessary.
  • Capitalized the first character in the noun Docker when using outside a code-block.

Fixes #8036

@linux-foundation-easycla
Copy link

linux-foundation-easycla bot commented Nov 2, 2025

CLA Signed

The committers listed above are authorized under a signed CLA.

  • ✅ login: vitorvasc / name: Vitor Vasconcellos (2c94ca4)

@otelbot-docs otelbot-docs bot requested review from a team November 2, 2025 07:50
@vitorvasc
Copy link
Member

/fix:format

@otelbot-docs
Copy link
Contributor

otelbot-docs bot commented Nov 3, 2025

fix:format applied successfully in run 19030053475.

@vitorvasc
Copy link
Member

Hi @network-charles, thanks for your contribution! Really appreciate it. 😄

We currently have some reusable includes and snippets that could be very helpful here. They're meant to describe setup and usage not only for Jaeger, but also for other backends like Prometheus and Zipkin — which helps us keep the docs consistent across languages and guides.

You can find the Jaeger include here: content/en/docs/languages/_includes/exporters/jaeger.md, and you can import it in the page using:

{{% include "exporters/jaeger.md" %}}

As a reference, the Python / Exporters page shows how these includes look when rendered in the docs: https://deploy-preview-8316--opentelemetry.netlify.app/docs/languages/python/exporters.

It might make sense to update the Ruby / Exporters page to use this include and, if possible, extend it to cover usage examples for other backends as well. WDYT?

@open-telemetry/docs-approvers @open-telemetry/ruby-contrib-approvers @open-telemetry/ruby-approvers any thoughts on this approach?

@network-charles
Copy link
Author

network-charles commented Nov 4, 2025

It's a pleasure, @vitorvasc.

The reusable Jaeger snippet is nice. The only issue now is the Docker command. It has additional ports.

From the Ruby exporters page:

docker run -d --name jaeger \
  -e COLLECTOR_ZIPKIN_HOST_PORT=:9411 \
  -e COLLECTOR_OTLP_ENABLED=true \
  -p 6831:6831/udp \
  -p 6832:6832/udp \
  -p 5778:5778 \
  -p 16686:16686 \
  -p 4317:4317 \
  -p 4318:4318 \
  -p 14250:14250 \
  -p 14268:14268 \
  -p 14269:14269 \
  -p 9411:9411 \
  jaegertracing/all-in-one:latest

Jaeger snippet:

docker run --rm \
  -e COLLECTOR_ZIPKIN_HOST_PORT=:9411 \
  -p 16686:16686 \
  -p 4317:4317 \
  -p 4318:4318 \
  -p 9411:9411 \
  jaegertracing/all-in-one:latest

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

Clarify UI port after running Ruby OTLP exporter Docker command

3 participants