Migrate from SignalFx Smart Agent to the Splunk Distribution of OpenTelemetry Collector 🔗
The SignalFx Smart Agent has reached End of Support. While the agent can capture and export telemetry to Splunk Observability Cloud, Splunk no longer provides any support, feature updates, security, or bug fixes. Such requests are not bound by any SLAs.
Note that this only affects the agent; Smart Agent receivers bundled in the Splunk Distribution of OpenTelemetry Collector are available and supported.
The Splunk Distribution of the OpenTelemetry Collector provides a unified way to receive, process, and export metrics, traces, and logs to Splunk Observability Cloud. Current SignalFx Smart Agent (deprecated) users can easily transition to the Collector without losing any functionality.
The benefits of using the Collector are:
Open standard based on OpenTelemetry.
Support for new features such as code profiling.
Ability to correlate data between different views within Splunk Observability Cloud with Related Content.
Fluentd for log collection, deactivated by default for Linux and Windows.
To migrate from the Smart Agent to the Collector, follow these steps.
While the Smart Agent is deprecated, Smart Agent monitors are not.
The Smart Agent metric monitors allow real-time insights into how your target services and applications are performing. These metric gathering utilities have an equivalent counterpart in the Collector.
Splunk Observability Cloud provides a translation tool to help you adapt your Smart Agent YAML configuration file to a YAML that you can use with the Collector.
Splunk Observability Cloud also has a mapping service that defines equivalencies between legacy Smart Agent metric naming and semantic conventions to the OpenTelemetry names and formats for metrics and metric metadata. See Metric mapping service for more information.
sfxagent.hostmetadata metric tracks the amount of Smart Agent instances installed in your environment.