-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
Open Telemetry extension Traces and Logs are not linked with the span #43626
Comments
/cc @brunobat (opentelemetry,tracing), @radcortez (opentelemetry,tracing) |
@lordofthejars can you please share your sample application? |
Sure: https://github.com/lordofthejars/quarkus-loki It is the same of the documentation |
🙏🏽 |
I tried this and it worked for me (after making sure that all the services were up and running) |
This might have been a bug from the previous Grafana image. @lordofthejars can you please retest with current Quarkus main? |
Going to update the repo and try again |
Yes it works. Thanks |
Thanks for checking |
Describe the bug
I found one issue that may be because I didn't use it correctly or because there is a bug it doesn't work from my understanding; I created the example in the documentation, and using the lgtm dev service, I started everything.
Then, Prometheus metrics, traces, and logs are there, so data is stored, but when I go to the trace, select a trace (by span ID), click the logs icon, and execute the query to Loki with the service name and span ID, it finds no logs.
So if I query logs by only the service name, all logs are there but it seems like the relationship with the span is not stored.
As I said I might have done something wrong, or I might be missing something.
@loicmathieu
Expected behavior
When I click log button from a specific span, it shows the logthe
Actual behavior
Not showing the log
How to Reproduce?
No response
Output of
uname -a
orver
No response
Output of
java -version
No response
Quarkus version or git rev
999-SNAPSHOT (9927819)
Build tool (ie. output of
mvnw --version
orgradlew --version
)No response
Additional information
It comes from this PR #38239
The text was updated successfully, but these errors were encountered: