diff --git a/gdi/integrations-list.rst b/gdi/integrations-list.rst index 2b521e37a..2a475cd3e 100644 --- a/gdi/integrations-list.rst +++ b/gdi/integrations-list.rst @@ -152,7 +152,7 @@ These are the available Smart Agent monitors:

Notification servicesΒΆ

-These integrations let you send Splunk Observability Cloud alert notifications to the following third-party notification services: +These integrations let you send Splunk Observability Cloud alert notifications to the following notification services: - Amazon EventBridge - BigPanda @@ -163,6 +163,7 @@ These integrations let you send Splunk Observability Cloud alert notifications t - ServiceNow - Slack - Splunk On-Call +- Splunk platform - Webhook - xMatters diff --git a/gdi/monitors-monitoring/signalfx-forwarder.rst b/gdi/monitors-monitoring/signalfx-forwarder.rst index b31064e49..c3ebaf8e6 100644 --- a/gdi/monitors-monitoring/signalfx-forwarder.rst +++ b/gdi/monitors-monitoring/signalfx-forwarder.rst @@ -4,11 +4,11 @@ SignalFx Forwarder (deprecated) ================================== .. meta:: - :description: Use this Splunk Observability Cloud integration for the SignalFX forwarder receiver. See benefits, install, configuration, and metrics + :description: Use this Splunk Observability Cloud integration for the SignalFx forwarder. See benefits, install, configuration, and metrics .. 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 ` GitHub documentation. -The Splunk Distribution of OpenTelemetry Collector uses the Smart Agent receiver with the +The Splunk Distribution of the OpenTelemetry Collector uses the Smart Agent receiver with the ``signalfx-forwarder`` monitor type to run an HTTP server that listens for data points and trace spans, and forward them to Splunk Observability Cloud. This integration supports the latest formats for diff --git a/gdi/opentelemetry/exposed-endpoints.rst b/gdi/opentelemetry/exposed-endpoints.rst index e186c58d2..cd396c8fb 100644 --- a/gdi/opentelemetry/exposed-endpoints.rst +++ b/gdi/opentelemetry/exposed-endpoints.rst @@ -39,7 +39,7 @@ See the table for a complete list of exposed ports and endpoints: * - ``http(s)://localhost:8006`` - Fluent forward receiver * - ``http(s)://0.0.0.0:9080`` - - Smart Agent receiver with :new-page:`SignalFx Forwarder ` monitor type (deprecated) + - Smart Agent receiver with the :ref:`signalfx-forwarder` * - ``http(s)://0.0.0.0:9411/api/[v1|v2]/spans`` - Zipkin receiver supporting V1 and V2 * - ``http(s)://0.0.0.0:9943`` diff --git a/gdi/opentelemetry/smart-agent/smart-agent-migration-monitors.rst b/gdi/opentelemetry/smart-agent/smart-agent-migration-monitors.rst index 62402b47f..4575b7120 100644 --- a/gdi/opentelemetry/smart-agent/smart-agent-migration-monitors.rst +++ b/gdi/opentelemetry/smart-agent/smart-agent-migration-monitors.rst @@ -38,7 +38,7 @@ For each Smart Agent monitor you want to add to the Collector, add a ``smartagen Instead of using ``discoveryRule``, use the Collector receiver creator and observer extensions. See :ref:`receiver-creator-receiver` for more information. -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 `. +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 `. Configure the Smart Agent receiver ------------------------------------------------------------