-
Notifications
You must be signed in to change notification settings - Fork 33
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.
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
Deploy Jaeger #280
Comments
For help with clarifying this task, what was the reason for deploying Jaeger? Was it just for generating trace data (functionality which has been sunset in favor of OpenTelemetry)? Or did we want to use Jaeger for its collector / query tooling? Both? |
I don't know if @pacomf has more context maybe. From my conversations with Iskandar I know that we would like to use |
this is the part I'm not 100% clear on: Jaeger uses the OpenTelemetry collector as its source for metrics. Assuming I'm understanding everything correctly, I think it'd be simplest to set up a flow like this: Pod -> OTel collector -> Prometheus versus trying to add Jaeger into the stack (either between the collector / prometheus or as its own endpoint). May make sense to wait on this one until everyone's back and we can discuss... |
Sure! Let's do that 😄 |
@IceKhan13 now that everyone's back, wanted to follow up on this one to get your thoughts |
Agree with you @psschwei. We will only need to switch Only thing matter is an ability to see traces / runtimes of spans :) |
I would say yes? I was taking a look to the configuration that Ray has for https://docs.ray.io/en/latest/ray-observability/ray-metrics.html |
It doesn't cover the trace span. It covers only metric span. |
I think we need Jaeger for the distributed trace span in qs-observability for local install |
I added instructions to install Jaeger in the local install in the README. I close this. |
What is the expected behavior?
Deploy Jaeger to the system.
Expose jaeger to grafana dashboard if possible (maybe avoid Jaeger and emit directly prometheus from opentelemetry spans).
Epic #139
The text was updated successfully, but these errors were encountered: