From 3b2d5bca3e0d7df78ab8a3041ce1503f6081edcc Mon Sep 17 00:00:00 2001 From: Miguel Alexandre Date: Tue, 7 Mar 2023 16:13:59 +0100 Subject: [PATCH] Docs: Include OTLP in the tracing references (#56806) --- docs/sources/setup-grafana/set-up-grafana-monitoring.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/sources/setup-grafana/set-up-grafana-monitoring.md b/docs/sources/setup-grafana/set-up-grafana-monitoring.md index 6634404fc9a..d520a4cba2e 100644 --- a/docs/sources/setup-grafana/set-up-grafana-monitoring.md +++ b/docs/sources/setup-grafana/set-up-grafana-monitoring.md @@ -14,13 +14,13 @@ weight: 800 # 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). 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