From faf9323fa9e43768bdf59f0d7f396ae769207275 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Gergely=20Madar=C3=A1sz?= Date: Mon, 9 Dec 2024 21:39:14 +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 16876f630..a7f7a5234 100644 --- a/docs/sources/reference/components/otelcol/otelcol.exporter.loadbalancing.md +++ b/docs/sources/reference/components/otelcol/otelcol.exporter.loadbalancing.md @@ -70,7 +70,7 @@ for metric collection. Otherwise, metrics for the same services would be sent to - `"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. -The loadbalancer will configure the exporter for the singal types supported by the `routing_key` +The loadbalancer configures the exporter for the signal types supported by the `routing_key`. Metrics support in `otelcol.exporter.loadbalancing` is considered experimental, so an exporter will be configured for metrics only if Alloy is run with `--stability-level=experimental`