Skip to content
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

Ruby example span profiles not working #3853

Closed
nateberkopec opened this issue Jan 19, 2025 · 5 comments
Closed

Ruby example span profiles not working #3853

nateberkopec opened this issue Jan 19, 2025 · 5 comments
Assignees

Comments

@nateberkopec
Copy link

Describe the bug

AFAICT span profiles/Tempo connection isn't working in the Ruby language example.

To Reproduce

Steps to reproduce the behavior:

  1. Start the Ruby rideshare example.
  2. I should see some traces in Explore -> Tempo, e.g. with a blank query. I don't see anything.

Environment

Following instructions using docker compose.

@marcsanmi marcsanmi self-assigned this Jan 20, 2025
@marcsanmi
Copy link
Contributor

marcsanmi commented Jan 20, 2025

Hi, @nateberkopec,

Thanks for reporting this.

I believe this is because of the breaking change introduced in the latest tempo release where the Open-Telemetry Collector receiver will connect to localhost instead of all interfaces 0.0.0.0.

For more details see grafana/tempo#4465.

I'd say is just a matter of updating tempo.yml. I'll work on this since it might affect other examples.

@marcsanmi
Copy link
Contributor

Closing this since it was already fixed in #3855. Feel free to reopen if something arises.

@nateberkopec
Copy link
Author

After this change, I no longer see Tempo in the Explore tab or under Data Sources.

I also see in the logs:

eu-north-1        | I, [2025-01-22T03:24:45.547374 #7]  INFO -- : [357620f4-89c5-4436-8a60-d69f631909e0] Processing by CarController#index as */*
ap-south-1        | E, [2025-01-22T03:24:46.682577 #7] ERROR -- : OpenTelemetry error: unexpected error in Jaeger::CollectorExporter#export - Failed to open TCP connection to localhost:14268 (Connection refused - connect(2) for "localhost" port 14268)
ap-south-1        | E, [2025-01-22T03:24:46.682603 #7] ERROR -- : OpenTelemetry error: Unable to export 9 spans
eu-north-1        | E, [2025-01-22T03:24:46.837973 #7] ERROR -- : OpenTelemetry error: unexpected error in Jaeger::CollectorExporter#export - Failed to open TCP connection to localhost:14268 (Connection refused - connect(2) for "localhost" port 14268)
eu-north-1        | E, [2025-01-22T03:24:46.938776 #7] ERROR -- : OpenTelemetry error: Unable to export 3 spans

@nateberkopec
Copy link
Author

FWIW I would also be happy to try this out on play.grafana.org, but the Tempo connection there seems to only be setup for the Go rideshare demo.

@benedictfischer09
Copy link

Looking at the docker-compose.yml file for the Pyroscope Ruby rideshare example it doesn't look like tempo is included as a service in that example

However, Pyroscope is included in the tracing example https://github.com/grafana/pyroscope/tree/main/examples/tracing/ruby

When I followed that readme I was able to test out the Span Profiles functionality in Tempo

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants