From 84bc959631d8ea4808b33a90db8be0288b2f67f4 Mon Sep 17 00:00:00 2001 From: Dmitrii Anoshin Date: Tue, 17 Dec 2024 09:40:08 -0800 Subject: [PATCH] [chore] [exporter/signalfx] Update trace correlation docs (#36866) Don't mention SAPM exporter since it's going to be deprecated. It doesn't matter which exporter is used to send traces. --- exporter/signalfxexporter/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/exporter/signalfxexporter/README.md b/exporter/signalfxexporter/README.md index ad988488ee57..043ef34e4590 100644 --- a/exporter/signalfxexporter/README.md +++ b/exporter/signalfxexporter/README.md @@ -150,7 +150,7 @@ Information about queued retry configuration parameters can be found ## Traces Configuration (correlation only) -:warning: _Note that traces must still be sent in using [sapmexporter](../sapmexporter) to see them in SignalFx._ +:warning: _Note that traces must still be sent to Splunk Observability via a separate trace exporter._ When traces are sent to the signalfx exporter it correlates traces to metrics. When a new service or environment is seen it associates the source (e.g. host or pod) to that service or environment in SignalFx. Metrics can then be