From c3d4086b769c2e1a8e6f5686e7ed80dab97b591d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Gergely=20Madar=C3=A1sz?= Date: Mon, 9 Dec 2024 21:39:37 +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 | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/docs/sources/reference/components/otelcol/otelcol.exporter.loadbalancing.md b/docs/sources/reference/components/otelcol/otelcol.exporter.loadbalancing.md index a7f7a5234..99f003f08 100644 --- a/docs/sources/reference/components/otelcol/otelcol.exporter.loadbalancing.md +++ b/docs/sources/reference/components/otelcol/otelcol.exporter.loadbalancing.md @@ -72,8 +72,9 @@ for metric collection. Otherwise, metrics for the same services would be sent to 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` +> **EXPERIMENTAL**: Metrics support in `otelcol.exporter.loadbalancing` is an [experimental][] feature. +> Experimental features are subject to frequent breaking changes, and may be removed with no equivalent replacement. +> The `stability.level` flag must be set to `experimental` to use the feature. ## Blocks