Documentation forAppOptics

Influxdb Listener

This plugin is currently being groomed to be an integration. It works, but we haven't spent a lot of time on it yet to optimize the user experience. Feel free to try it out, just keep in mind that we will be enhancing the experience over time.

This plugin is ported from the Telegraf Socket Listener Service Input Plugin. The Influxdb Listener is a service input plugin that listens for messages from the InfluxDB Line Protocol.


The influxdb_listener plugin is included with the SolarWinds Snap Agent by default, please follow the directions below to enable it for a agent instance.


The agent provides an example configuration file to help you get started quickly. It defines the plugin and task file to be loaded by the agent, but requires you to provide the correct settings for your installation. To enable the plugin:

  1. Make a copy of the influxdb_listener example configuration file /opt/SolarWinds/Snap/etc/plugins.d/influxdb_listener.yaml.example, renaming it to /opt/SolarWinds/Snap/etc/plugins.d/influxdb_listener.yaml:
$ sudo cp /opt/SolarWinds/Snap/etc/plugins.d/influxdb_listener.yaml.example /opt/SolarWinds/Snap/etc/plugins.d/influxdb_listener.yaml
  1. Update the /opt/SolarWinds/Snap/etc/plugins.d/influxdb_listener.yaml configuration file with settings specific to your use case, for example:
      ## URL to listen on
      # service_address: "tcp://:8094"
      # service_address: "tcp://"
      # service_address: "tcp4://:8094"
      # service_address: "tcp6://:8094"
      # service_address: "tcp6://[2001:db8::1]:8094"
      # service_address: "udp://:8094"
      # service_address: "udp4://:8094"
      # service_address: "udp6://:8094"
      # service_address: "unix:///tmp/graphite.sock"
      # service_address: "unixgram:///tmp/graphite.sock"
      ## Maximum number of concurrent connections.
      ## Only applies to stream sockets (e.g. TCP).
      ## 0 (default) is unlimited.
      # max_connections: 1024
      ## Read timeout.
      ## Only applies to stream sockets (e.g. TCP).
      ## 0 (default) is unlimited.
      # read_timeout: "30s"
      ## Maximum socket buffer size in bytes.
      ## For stream sockets, once the buffer fills up, the sender will start backing up.
      ## For datagram sockets, once the buffer fills up, metrics will start dropping.
      ## Defaults to the OS default.
      # read_buffer_size: 65535
      ## Period between keep alive probes.
      ## Only applies to TCP sockets.
      ## 0 disables keep alive probes.
      ## Defaults to the OS configuration.
      # keep_alive_period: "5m"
      ## Metric name prefix
      bridge_prefix: "influx"
      # bridge_prefix: ""
  plugin: snap-plugin-collector-bridge-influxdb_listener
  task: task-bridge-influxdb_listener.yaml
  1. Restart the agent:
$ sudo service swisnapd restart
  1. Enable the Influxdb plugin

    When you log in to AppOptics you should see Influxdb listed in the Plugin section on the home page. You will also find it on the Integrations Page. Clicking on the widget will open up a window that shows you the list of metrics that the plugin is collecting. Activate the plugin by clicking on the "Enable Plugin" button, then select the metrics you would like to see on a dashboard and click on the "Send Metrics to Dashboard" button.


The collected metrics will be prefixed with influx.* in AppOptics (or the configured value for bridge_prefix on the plugin configuration).

For more information read the Telegraf Socket Listener Service Input Plugin docs.

The scripts are not supported under any SolarWinds support program or service. The scripts are provided AS IS without warranty of any kind. SolarWinds further disclaims all warranties including, without limitation, any implied warranties of merchantability or of fitness for a particular purpose. The risk arising out of the use or performance of the scripts and documentation stays with you. In no event shall SolarWinds or anyone else involved in the creation, production, or delivery of the scripts be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the scripts or documentation.