-
Notifications
You must be signed in to change notification settings - Fork 155
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
Render: Support tracing #164
Labels
Comments
github-project-automation
bot
moved this to 🗂️ Needs Triage / Escalation
in Sharing squad
Oct 20, 2023
Info: |
Reading material recommended:
Local Setup:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Grafana supports both reporting spans and forwarding tracing IDs. It would be great if the image renderer could do so as well (or at least forward the tracing ID back to grafana).
That would enable an unbroken trace from an image rendering request (or even before that) all the way to the datasource like e.g. prometheus, which has recently added support for tracing as well.
Right now when rendering images, you see two independent traces being reported: One for the original request, and one by the image-renderer when it calls back to grafana.
The text was updated successfully, but these errors were encountered: