-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Add jaeger as datasource to Grafana #319
Conversation
Looks good! I think the grafana bullet point in the main README could also be updated to mention traces. |
Any reason why do we need that in this demo? |
Co-authored-by: Reiley Yang <[email protected]>
Co-authored-by: Reiley Yang <[email protected]>
@julianocosta89 it's an out of the box feature of Grafana. - It enables viewing traces and metrics side by side and stays in the OpenSource track. Jaeger is still the main store for the trace data. - Hence I dont think there is an issue adding this. It's lesser a thing we need in the demo, but we get it for free - why not enable it? |
No no... Just wanted to know what was that 😅 As we are already talking, let me ask you one thing. |
Alright :) Sure thing - Grafana can provision dashboards from file as well - makes sense to add a set of curated dashboards to the demo. https://grafana.com/docs/grafana/latest/administration/provisioning/#dashboards |
I would consider this one finished for now - dashboards would be a separate PR :) |
* Add jaeger as datasource to Grafana * Update src/grafana/provisioning/datasources/jaeger.yaml Co-authored-by: Reiley Yang <[email protected]> * Update src/grafana/provisioning/datasources/default.yaml Co-authored-by: Reiley Yang <[email protected]> Co-authored-by: Carter Socha <[email protected]> Co-authored-by: Reiley Yang <[email protected]> Co-authored-by: Pierre Tessier <[email protected]>
This adds jaeger as a datasource for trace data to Grafana when provisioning.