Telegraf Varnish 🔗
The Splunk Distribution of OpenTelemetry Collector provides this integration as the
telegraf/varnish monitor via the Smart Agent Receiver. This is an embedded form of the Telegraf Varnish plugin. This monitor uses the
varnishstat command, so the Smart Agent needs to be run on the same host as the varnish server.
Do the following to enable the Smart Agent to run the
usermod -a -G varnish signalfx-agent
This monitor is available in the SignalFx Smart Agent Receiver, which is part of the Splunk Distribution of OpenTelemetry Collector.
To install this integration:
Deploy the Splunk Distribution of OpenTelemetry Collector to your host or container platform.
Configure the monitor, as described in the next section.
This Splunk Distribution of OpenTelemetry Collector allows embedding a Smart Agent monitor configuration in an associated Smart Agent Receiver instance.
Note: Providing a Telegraf Varnish monitor entry in your Smart Agent or Collector configuration is required for its use. Use the appropriate form for your agent type.
Smart Agent 🔗
To activate this monitor in the Smart Agent, add the following to your agent configuration:
monitors: # All monitor config goes under this key - type: telegraf/varnish ... # Additional config
See Smart Agent example configuration for an autogenerated example of a YAML configuration file, with default values where applicable.
Splunk Distribution of OpenTelemetry Collector 🔗
To activate this monitor in the Splunk Distribution of OpenTelemetry Collector, add the following to your agent configuration:
receivers: smartagent/varnish: type: telegraf/varnish ... # Additional config
See configuration examples for specific use cases that show how the Splunk OpenTelemetry Collector can integrate and complement existing environments.
Note: Include monitors with event-sending functionality as members of a
logs pipeline that utilizes an exporter that makes the event submission requests. Use a Resource Detection processor to ensure that host identity and other useful information is made available as event dimensions.
Configuration settings 🔗
The following table shows the configuration options for this monitor:
||If running as a restricted user, enable this flag to prepend sudo. (default:
||The location of the varnishstat binary. (default:
||Which stats to gather. Glob matching can be used (for example,
||Optional name for the varnish instance to query. It corresponds to a
The following metrics are available for this integration:
If you are not able to see your data in Splunk Observability Cloud: