From 8c69571ca8a7c1c803ceb62d7c1ae938667661a9 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Gergely=20Madar=C3=A1sz?= Date: Mon, 9 Dec 2024 21:39:00 +0100 Subject: [PATCH] Update docs/sources/reference/components/otelcol/otelcol.exporter.loadbalancing.md Co-authored-by: Clayton Cornell <131809008+clayton-cornell@users.noreply.github.com> --- .../components/otelcol/otelcol.exporter.loadbalancing.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/sources/reference/components/otelcol/otelcol.exporter.loadbalancing.md b/docs/sources/reference/components/otelcol/otelcol.exporter.loadbalancing.md index b6253508e..cfe7129c1 100644 --- a/docs/sources/reference/components/otelcol/otelcol.exporter.loadbalancing.md +++ b/docs/sources/reference/components/otelcol/otelcol.exporter.loadbalancing.md @@ -65,7 +65,7 @@ The `routing_key` attribute determines how to route signals across endpoints. It - `"service"`: spans, logs, and metrics with the same `service.name` will be exported to the same backend. This is useful when using processors like the span metrics, so all spans for each service are sent to consistent {{< param "PRODUCT_NAME" >}} instances for metric collection. Otherwise, metrics for the same services would be sent to different instances, making aggregations inaccurate. -- `"traceID"`: spans/logs belonging to the same traceID will be exported to the same backend. +- `"traceID"`: spans and logs belonging to the same `traceID` will be exported to the same backend. - `"resource"`: metrics belonging to the same resource will be exported to the same backend. - `"metric"`: metrics with the same name will be exported to the same backend. - `"streamID"`: metrics with the same streamID will be exported to the same backend