Smart Agent receiver ๐
The Smart Agent receiver is a native OTel component that lets you use Smart Agent monitors through the Splunk Distribution of the OpenTelemetry Collector. Supported pipeline types are traces
, metrics
, and logs
. See Process your data with pipelines for more information.
The Smart Agent receiver is fully supported only on AMD64 Linux and Windows platforms. Support for ARM64 is experimental starting from the Splunk Distribution of OpenTelemetry Collector version 0.73 and higher.
Note
For instructions on how to migrate from the Smart Agent to the Splunk Distribution of OpenTelemetry Collector, see Migrate from SignalFx Smart Agent to the Splunk Distribution of OpenTelemetry Collector.
Supported monitors ๐
The Smart Agent bundle provides the following monitor types for each platform:
Platform |
Monitor types |
---|---|
Linux (AMD64 and ARM64) |
|
Windows (AMD64) |
|
For more information about monitors included in the agent bundle, see Subprocess Smart Agent monitors.
Native Smart Agent monitors ๐
Native Smart Agent monitors are grouped into three types:
Standalone
Prometheus
Telegraf
The following matrices list support for each monitor in each architecture.
Support for native standalone monitors
Monitor |
Support for AMD64 Linux |
Support for AMD64 Windows |
Support for ARM64 Linux |
Support for ppc64le Linux |
---|---|---|---|---|
|
Yes |
Yes |
Yes |
Yes |
|
Yes |
Yes |
Yes |
Yes |
|
Yes |
Yes |
Yes |
Yes |
|
Yes |
Yes |
Yes |
Yes |
|
Yes |
Yes |
Yes |
Yes |
|
Yes |
Yes |
Yes |
Yes |
|
Yes |
Yes |
Yes |
Yes |
|
Yes |
Yes |
Yes |
Yes |
|
Yes |
Yes |
Yes |
No |
|
Yes |
Yes |
Yes |
Yes |
|
Yes |
Yes |
Yes |
Yes |
|
Yes |
Yes |
Yes |
Yes |
|
Yes |
Yes |
Yes |
Yes |
|
Yes |
Yes |
Yes |
Yes |
|
Yes |
Yes |
Yes |
Yes |
|
Yes |
Yes |
Yes |
Yes |
|
Yes |
Yes |
Yes |
Yes |
|
Yes |
Yes |
Yes |
Yes |
|
Yes |
Yes |
Yes |
Yes |
|
Yes |
Yes |
Yes |
Yes |
|
Yes |
Yes |
Yes |
Yes |
|
Yes |
Yes |
Yes |
Yes |
|
Yes |
Yes |
Yes |
Yes |
|
Yes |
Yes |
Yes |
Yes |
|
Yes |
Yes |
Yes |
Yes |
|
Yes |
Yes |
Yes |
Yes |
|
Yes |
Yes |
Yes |
Yes |
|
Yes |
Yes |
Yes |
Yes |
|
Yes |
Yes |
Yes |
Yes |
|
Yes |
Yes |
Yes |
Yes |
|
Yes |
Yes |
Yes |
Yes |
|
Yes |
Yes |
Yes |
Yes |
|
Yes |
Yes |
Yes |
Yes |
|
Yes |
Yes |
Yes |
Yes |
|
Yes |
Yes |
Yes |
Yes |
|
Yes |
Yes |
Yes |
Yes |
|
Yes |
Yes |
Yes |
Yes |
|
Yes |
Yes |
Yes |
Yes |
Support for native Prometheus monitors
Monitor |
Support for AMD64 Linux |
Support for AMD64 Windows |
Support for ARM64 Linux |
Support for ppc64le Linux |
---|---|---|---|---|
|
Yes |
Yes |
Yes |
Yes |
|
Yes |
Yes |
Yes |
Yes |
|
Yes |
Yes |
Yes |
Yes |
|
Yes |
Yes |
Yes |
Yes |
|
Yes |
Yes |
Yes |
Yes |
|
Yes |
Yes |
Yes |
Yes |
|
Yes |
Yes |
Yes |
Yes |
|
Yes |
Yes |
Yes |
Yes |
|
Yes |
Yes |
Yes |
Yes |
|
Yes |
Yes |
Yes |
Yes |
|
Yes |
Yes |
Yes |
Yes |
|
Yes |
Yes |
Yes |
Yes |
Support for native Telegraf monitors
Monitor |
Support for AMD64 Linux |
Support for AMD64 Windows |
Support for ARM64 Linux |
Support for ppc64le Linux |
---|---|---|---|---|
|
Yes |
Yes |
Yes |
Yes |
|
Yes |
Yes |
Yes |
Yes |
|
Yes |
Yes |
Yes |
Yes |
|
Yes |
Yes |
Yes |
Yes |
|
Yes |
Yes |
Yes |
Yes |
|
Yes |
Yes |
Yes |
Yes |
|
No |
Yes |
No |
No |
|
Yes |
Yes |
Yes |
Yes |
|
Yes |
Yes |
Yes |
Yes |
|
Yes |
Yes |
Yes |
Yes |
|
Yes |
Yes |
Yes |
Yes |
|
No |
Yes |
No |
No |
|
No |
Yes |
No |
No |
|
No |
Yes |
No |
No |
Subprocess Smart Agent monitors ๐
Support for Smart Agent receiver monitor types is experimental for ARM64 starting from the Splunk Distribution of OpenTelemetry Collector version 0.73 and higher. Using the Smart Agent receiver with monitor types is not supported for ppc64le architectures.
Subprocess monitor types are those that initiate the creation and management of a child process where metric gathering occurs. There are three major subprocess monitor types:
collectd
and its associatedcollectd/GenericJMX
plugin-based integrationssfxcollectd
JMX
These types derive from integrations that produce metrics in the Smart Agent and are not reflective of the current ability to run arbitrary Python or Java applications.
Support for collectd subprocess monitors
Monitor |
Support for AMD64 Linux |
Support for AMD64 Windows |
Support for ARM64 Linux |
Support for ppc64le Linux |
---|---|---|---|---|
|
Yes |
No |
Experimental |
No |
|
Yes |
No |
Experimental |
No |
|
Yes |
No |
Experimental |
No |
|
Yes |
No |
Experimental |
No |
|
Yes |
No |
Experimental |
No |
|
Yes |
No |
Experimental |
No |
|
Yes |
No |
Experimental |
No |
|
Yes |
No |
Experimental |
No |
|
Yes |
No |
Experimental |
No |
|
Yes |
No |
Experimental |
No |
Support for collectd or GenericJMX subprocess monitors
Monitor |
Support for AMD64 Linux |
Support for AMD64 Windows |
Support for ARM64 Linux |
Support for ppc64le Linux |
---|---|---|---|---|
|
Yes |
No |
Experimental |
No |
|
Yes |
No |
Experimental |
No |
|
Yes |
No |
Experimental |
No |
|
Yes |
No |
Experimental |
No |
|
Yes |
No |
Experimental |
No |
|
Yes |
No |
Experimental |
No |
Support for sfxcollectd Python subprocess monitors
Monitor |
Support for AMD64 Linux |
Support for AMD64 Windows |
Support for ARM64 Linux |
Support for ppc64le Linux |
---|---|---|---|---|
|
Yes |
Yes |
Experimental |
No |
|
Yes |
Yes |
Experimental |
No |
|
Yes |
Yes |
Experimental |
No |
|
Yes |
Yes |
Experimental |
No |
|
Yes |
Yes |
Experimental |
No |
|
Yes |
Yes |
Experimental |
No |
|
Yes |
Yes |
Experimental |
No |
|
Yes |
Yes |
Experimental |
No |
|
Yes |
Yes |
Experimental |
No |
|
Yes |
Yes |
Experimental |
No |
|
Yes |
Yes |
Experimental |
No |
|
Yes |
Yes |
Experimental |
No |
|
Yes |
Yes |
Experimental |
No |
|
Yes |
Yes |
Experimental |
No |
Support for subprocess JMX monitors
Monitor |
Support for AMD64 Linux |
Support for AMD64 Windows |
Support for ARM64 Linux |
Support for ppc64le Linux |
---|---|---|---|---|
|
Yes |
Yes (requires JRE) |
Experimental |
No |
Benefits ๐
The Smart Agent receiver lets you use Smart Agent monitors through the OpenTelemetry Collector. In most cases, you can move your existing Smart Agent monitor configuration to the configuration file of the Collector without changes.
For a list of monitor data sources, see Supported integrations in Splunk Observability Cloud.
Get started ๐
By default, the Splunk Distribution of OpenTelemetry Collector includes the Smart Agent receiver with the processlist
monitor when deploying in host monitoring (agent) mode. See Collector deployment modes for more information.
For each Smart Agent monitor you want to add to the Collector, add a Smart Agent receiver. After youโve configured a Smart Agent monitor in the Collector, each Smart Agent receiver behaves like the corresponding Smart Agent monitor.
Sample configurations ๐
The following example adds the Postgresql monitor to the Collector using the Smart Agent receiver:
receivers:
smartagent/postgresql:
type: postgresql
host: mypostgresinstance
port: 5432
dimensionClients:
- signalfx # Instructs the receiver to use this exporter for dimension updates
You can then add the receiver to any compatible pipeline. For example:
service:
pipelines:
metrics:
receivers:
- smartagent/postgresql
exporters:
- signalfx
If you use a monitor that updates dimension properties or tags, for example postgresql
, add the name of your SignalFx exporter in the dimensionClients
field in Smart Agent receiver configuration block. If you donโt set any exporter in the dimensionClients
field, the receiver tries to use the pipeline to which itโs connected. If you donโt require dimension updates, you can use an empty array ([]
) to deactivate it.
Caution
Donโt remove the smartagent/processlist
receiver from the configuration. System processes and Smart Agent telemetry depend on the receiverโs configuration.
Add additional metrics ๐
To ingest additional metrics using Smart Agent monitors, add the extraMetrics
field to the monitor configuration. For example:
receivers:
smartagent/postgresql:
type: postgresql
host: mypostgresinstance
port: 5432
extraMetrics:
- actual-name-0 # Add metrics to be ingested
- actual-name-1
Settings ๐
To configure Smart Agent monitors, see the documentation on each monitor type in Supported integrations in Splunk Observability Cloud.
Troubleshooting ๐
If you are a Splunk Observability Cloud customer and are not able to see your data in Splunk Observability Cloud, you can get help in the following ways.
Available to Splunk Observability Cloud customers
Submit a case in the Splunk Support Portal .
Contact Splunk Support .
Available to prospective customers and free trial users
Ask a question and get answers through community support at Splunk Answers .
Join the Splunk #observability user group Slack channel to communicate with customers, partners, and Splunk employees worldwide. To join, see Chat groups in the Get Started with Splunk Community manual.