Skip to content

Chore: jaeger guidance #4923

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: v1.16
Choose a base branch
from
+9 −1
Open

Chore: jaeger guidance #4923

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
c9f4cfc
update Jaeger setup instructions for port conflict and background con…
MyMirelHub Oct 22, 2025
fb33211
fix spacing
MyMirelHub Oct 22, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 9 additions & 1 deletion ...rations/observability/tracing/otel-collector/open-telemetry-collector-jaeger.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,8 +17,10 @@ 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 \
Expand All @@ -27,6 +29,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:
Copy link
Member

@msfussell msfussell Oct 22, 2025 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The other edit you can do here is say that in the development environment navigate to the local dapr folder (add this reference link https://docs.dapr.io/getting-started/install-dapr-selfhost/#step-5-verify-components-directory-has-been-initialized) and update the default config.yaml file with these changes.

Can I also suggest that in this article https://docs.dapr.io/getting-started/install-dapr-selfhost/ we add an "Optional Step 6. Configure JaegerV2 for local tracing instead of Zipkin" and then add a link to this article. That is to give people a choice of the local tracing experience.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Other things to update

"1. Create a configuration file (e.g., tracing.yaml)" - Should be ->"1. Create a configuration file (for example tracing.yaml)

  1. Why install cert- manager? And if so, why is this setting isSecure: false. I would expect that we show how to install secure connect with a cert (hence cert-manager yes)?

  2. Is these namespace below correct between the deployment and when you say "opentelemetry-operator-system" namespace?

Confirm that all resources in the opentelemetry-operator-system namespace are ready.

Deploy a Jaeger V2 instance with in-memory storage:
Apply the following configuration to create a Jaeger V2 instance:

apiVersion: opentelemetry.io/v1beta1
kind: OpenTelemetryCollector
metadata:
  name: jaeger-inmemory-instance
  namespace: observability


> **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.
Expand Down
Loading