Chore: jaeger guidance

[MyMirelHub]

Description

• Added note about port 9411 conflict with Zipkin (which runs by default after dapr init)
• Included command to stop the dapr_zipkin container before starting Jaeger
• Updated docker run command to include -d flag to run Jaeger detached in the background

Issue reference

#4920

[msfussell]

More comments/updates

[msfussell]

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.

[msfussell]

Other things to update

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

2. 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)?

3. 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