smartagentreceiver

SignalFx Smart Agent Receiver

Note: The SignalFx Smart Agent receiver is fully supported only on x86_64/amd64 platforms. Support for arm64 platforms is currently experimental.

The Smart Agent Receiver lets you use SignalFx Smart Agent monitors in the Splunk Distribution of OpenTelemetry Collector. Many monitors also require a Smart Agent release bundle, which is installed by the Splunk Distribution of OpenTelemetry Collector on supported x86_64/amd64 platforms.

See the migration guide for more information about migrating from the Smart Agent to the Splunk Distribution of the OpenTelemetry Collector.

Beta: All Smart Agent monitors are supported by Splunk. Configuration and behavior may change without notice.

Configuration

For each Smart Agent monitor you want to add to the Collector, add a smartagent receiver configuration block. Once configured in the Collector, each smartagent receiver acts as a drop-in replacement for its corresponding Smart Agent monitor.

1. Put any Smart Agent or collectd configuration into the global Smart Agent Extension section of your Collector configuration.
2. Instead of using discoveryRule, use the Collector's Receiver Creator and Observer extensions.
3. If you're using a SignalFx Forwarder monitor, 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.
4. To replace or modify metrics, use Collector processors.
5. If you have a monitor that sends events (e.g. kubernetes-events, nagios, processlist, and some telegraf monitors like telegraf/exec), add it to a logs pipeline that uses a SignalFx exporter. It's recommended, and in the case of the Processlist monitor required, to put into the same pipeline a Resource Detection processor, which will add host information and other useful dimensions to the events. An example is provided below.
6. If you have a monitor that updates dimension properties or tags, for example ecs-metadata, heroku-metadata, kubernetes-cluster, openshift-cluster, postgresql, or sql, put the name of your SignalFx exporter in its dimensionClients field in the Collector's SignalFx receiver configuration block. If you don't specify any exporters in this array field, the receiver attempts to use the Collector pipeline to which it's connected. If the next element of the pipeline isn't compatible with updating dimensions, and if you configured a single SignalFx exporter, the receiver uses that SignalFx exporter. If you don't require dimension updates, you can specify the empty array [] to disable it.

Example:

receivers:
  smartagent/signalfx-forwarder:
    type: signalfx-forwarder
  smartagent/postgresql:
    type: postgresql
    host: mypostgresinstance
    port: 5432
    dimensionClients:
      - signalfx  # references the SignalFx Exporter configured below
  smartagent/processlist:
    type: processlist
  smartagent/kafka:
    type: collectd/kafka
    host: mykafkabroker
    port: 7099
    clusterName: mykafkacluster
    intervalSeconds: 5

processors:
  resourcedetection:
    detectors:
      - system

exporters:
  signalfx:
    access_token: "${SIGNALFX_ACCESS_TOKEN}"
    realm: us1
  sapm:
    access_token: "${SIGNALFX_ACCESS_TOKEN}"
    endpoint: https://ingest.us1.signalfx.com/v2/trace

service:
  pipelines:
    metrics:
      receivers:
        - smartagent/postgresql
        - smartagent/kafka
        - smartagent/signalfx-forwarder
      processors:
        - resourcedetection
      exporters:
        - signalfx
    logs:
      receivers:
        - smartagent/processlist
      processors:
        - resourcedetection
      exporters:
        - signalfx
    traces:
      receivers:
        - smartagent/signalfx-forwarder
      processors:
        - resourcedetection
      exporters:
        - sapm