Skip to content
This repository was archived by the owner on Sep 2, 2025. It is now read-only.

Commit f0dd17a

Browse files
Merge pull request #2321 from splunk/urbiz-OD6168-sfx-fwd
[6168]: Minor edits for Sfx fwd
2 parents 70e49fc + 297bd08 commit f0dd17a

File tree

3 files changed

+4
-4
lines changed

3 files changed

+4
-4
lines changed

gdi/monitors-monitoring/signalfx-forwarder.rst

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,11 +4,11 @@ SignalFx Forwarder (deprecated)
44
==================================
55

66
.. meta::
7-
:description: Use this Splunk Observability Cloud integration for the SignalFX forwarder receiver. See benefits, install, configuration, and metrics
7+
:description: Use this Splunk Observability Cloud integration for the SignalFx forwarder. See benefits, install, configuration, and metrics
88

99
.. note:: This integration is deprecated. If you're using the Splunk Distribution of the OpenTelemetry Collector and want to forward data to Splunk Observability Cloud, use the native OTLP receiver. See more at :new-page:`OTLP receiver <https://github.com/open-telemetry/opentelemetry-collector/tree/main/receiver/otlpreceiver>` GitHub documentation.
1010

11-
The Splunk Distribution of OpenTelemetry Collector uses the Smart Agent receiver with the
11+
The Splunk Distribution of the OpenTelemetry Collector uses the Smart Agent receiver with the
1212
``signalfx-forwarder`` monitor type to run an HTTP server that listens
1313
for data points and trace spans, and forward them to Splunk
1414
Observability Cloud. This integration supports the latest formats for

gdi/opentelemetry/exposed-endpoints.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -39,7 +39,7 @@ See the table for a complete list of exposed ports and endpoints:
3939
* - ``http(s)://localhost:8006``
4040
- Fluent forward receiver
4141
* - ``http(s)://0.0.0.0:9080``
42-
- Smart Agent receiver with :new-page:`SignalFx Forwarder <https://docs.splunk.com/Observability/gdi/signalfx-forwarder/signalfx-forwarder.html>` monitor type (deprecated)
42+
- Smart Agent receiver with the :ref:`signalfx-forwarder`
4343
* - ``http(s)://0.0.0.0:9411/api/[v1|v2]/spans``
4444
- Zipkin receiver supporting V1 and V2
4545
* - ``http(s)://0.0.0.0:9943``

gdi/opentelemetry/smart-agent/smart-agent-migration-monitors.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -38,7 +38,7 @@ For each Smart Agent monitor you want to add to the Collector, add a ``smartagen
3838

3939
Instead of using ``discoveryRule``, use the Collector receiver creator and observer extensions. See :ref:`receiver-creator-receiver` for more information.
4040

41-
If you're using a SignalFx Forwarder monitor (deprecated), add it to both a ``traces`` and a ``metrics`` pipeline, and use a Sapm exporter and a SignalFx exporter, as each pipeline's exporter, respectively. See more on :ref:`exporters <collector-components-processors>`.
41+
If you're using a SignalFx Forwarder monitor (deprecated), add it to both a ``traces`` and a ``metrics`` pipeline, and use a SAPM exporter and a SignalFx exporter, as each pipeline's exporter, respectively. See more on :ref:`exporters <collector-components-processors>`.
4242

4343
Configure the Smart Agent receiver
4444
------------------------------------------------------------

0 commit comments

Comments
 (0)