IntenseWebs/grafana
3
0
Fork 0
mirror of https://github.com/grafana/grafana.git synced 2025-02-25 18:55:37 -06:00
Code Issues Packages Projects Releases Wiki Activity

Docs: Include OTLP in the tracing references (#56806)

Browse Source
This commit is contained in:
Miguel Alexandre 2023-03-07 16:13:59 +01:00 committed by GitHub
parent 0c0d63b830
commit 3b2d5bca3e
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/sources/setup-grafana/set-up-grafana-monitoring.md
View File

@ -14,13 +14,13 @@ weight: 800
# Set up Grafana monitoring # Set up Grafana monitoring
Grafana supports [Jaeger tracing](https://www.jaegertracing.io/). Grafana supports tracing.
Grafana can emit Jaeger traces for its HTTP API endpoints and propagate Jaeger trace information to data sources. Grafana can emit Jaeger or OpenTelemetry Protocol (OTLP) traces for its HTTP API endpoints and propagate Jaeger and [w3c Trace Context](https://www.w3.org/TR/trace-context/) trace information to compatible data sources.
All HTTP endpoints are logged evenly (annotations, dashboard, tags, and so on). All HTTP endpoints are logged evenly (annotations, dashboard, tags, and so on).
When a trace ID is propagated, it is reported with operation 'HTTP /datasources/proxy/:id/\*'. When a trace ID is propagated, it is reported with operation 'HTTP /datasources/proxy/:id/\*'.
Refer to [Configuration]({{< relref "configure-grafana/#tracingjaeger" >}}) for information about enabling Jaeger tracing. Refer to [Configuration's OpenTelemetry section]({{< relref "configure-grafana/#tracingopentelemetry" >}}) for a reference of tracing options available in Grafana.
## View Grafana internal metrics ## View Grafana internal metrics