You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's look like docker-compose file in examples/grafana-integration is missing otel-collector port (4318) that cause missing tracing data on jaeger dashboard when you try to run grafana-integration example.
Steps to reproduce
cd examples/grafana-integration/
docker compose up -d
check jaeger dashboard
Expected behavior
tracing data from hotrod is missing
Relevant log output
Screenshot
No response
Additional context
No response
Jaeger backend version
No response
SDK
No response
Pipeline
No response
Stogage backend
No response
Operating system
No response
Deployment model
No response
Deployment configs
The text was updated successfully, but these errors were encountered:
@NuttakitDW
I have confirmed that the trace_id generated in Hotrod is present in the Jaeger UI when searched. However, the issue appears to be that the Hotrod service itself is not listed under the "Services" section, as shown in the image. Am I on the right track in assuming that the actual bug is the Hotrod service not appearing in the services list?
What happened?
It's look like docker-compose file in examples/grafana-integration is missing otel-collector port (4318) that cause missing tracing data on jaeger dashboard when you try to run grafana-integration example.
Steps to reproduce
Expected behavior
tracing data from hotrod is missing
Relevant log output
Screenshot
No response
Additional context
No response
Jaeger backend version
No response
SDK
No response
Pipeline
No response
Stogage backend
No response
Operating system
No response
Deployment model
No response
Deployment configs
The text was updated successfully, but these errors were encountered: