Docs » Available host and application monitors » Configure application receivers for hosts and servers » HAProxy

HAProxy 🔗

The Splunk Distribution of OpenTelemetry Collector uses the Smart Agent receiver with the HAProxy monitor type to monitor an HAProxy instance. This monitor requires HAProxy 1.5+.

Benefits 🔗

After you configure the integration, you can access these features:

  • View metrics. You can create your own custom dashboards, and most monitors provide built-in dashboards as well. For information about dashboards, see View dashboards in Observability Cloud.

  • View a data-driven visualization of the physical servers, virtual machines, AWS instances, and other resources in your environment that are visible to Infrastructure Monitoring. For information about navigators, see Splunk Infrastructure Monitoring navigators.

  • Access the Metric Finder and search for metrics sent by the monitor. For information, see Use the Metric Finder.

Set up 🔗

Socket configuration 🔗

The location of the HAProxy socket file is defined in the HAProxy configuration file, as shown in the following example:

    stats socket /var/run/haproxy.sock
    stats timeout 2m

Note: You can use a TCP socket for stats in HAProxy. In your haproxy plugin configuration file, specify the TCP address for the socket. For example, you can use In the haproxy.cfg file, change the stats socket to use the same TCP address and port, as shown in the following example:

    stats socket localhost:9000
    stats timeout 2m

To use a more restricted TCP socket, follow these steps:

  1. Define a backend server that listens to stats on localhost.

  2. Define a frontend proxy server that communicates with the back-end server on a different port.

  3. Use ACLs on both servers to control access. Depending on how restrictive your socket is, you might need to add the signalfx-agent user to the haproxy group as follows: sudo usermod -a -G haproxy signalfx-agent

The following configuration file shows how to define a back-end server and a frontend proxy:

    stats socket localhost:9000
    stats timeout 2m

backend stats-backend
    mode tcp
    server stats-localhost localhost:9000

frontend stats-frontend
    bind *:9001
    default_backend stats-backend
    acl ...
    acl ...

SELinux setup 🔗

If you have SELinux activated, create a SELinux policy package by downloading the type enforcement file to some place on your server. Run the following commands to create and install the policy package:

    $ checkmodule -M -m -o haproxy.mod haproxy.te
    checkmodule:  loading policy configuration from haproxy.te
    checkmodule:  policy configuration loaded
    checkmodule:  writing binary representation (version 17) to haproxy.mod
    $ semodule_package -o haproxy.pp -m haproxy.mod
    $ sudo semodule -i haproxy.pp
    $ sudo reboot

Installation 🔗

Follow these steps to deploy this integration:

  1. Deploy the Splunk Distribution of OpenTelemetry Collector to your host or container platform:

  2. Configure the monitor, as described in the Configuration section.

  3. Restart the Splunk Distribution of OpenTelemetry Collector.

Configuration 🔗

To use this integration of a Smart Agent monitor with the Collector:

  1. Include the Smart Agent receiver in your configuration file.

  2. Add the monitor type to the Collector configuration, both in the receiver and pipelines sections.

Example 🔗

To activate this integration, add the following to your Collector configuration:

        type: haproxy
        ...  # Additional config

Next, add the monitor to the service > pipelines > metrics > receivers section of your configuration file:

      monitors: [smartagent/haproxy]

Configuration options 🔗

The following table shows the configuration options for this monitor:








Path to a python binary that should be used to execute the Python code. If not set, a built-in runtime will be used. Can include arguments to the binary as well.







(default: 0)



list of strings

A list of all the pxname(s) or svname(s) that you want to monitor (e.g. ["http-in", "server1", "backend"])



list of strings

Deprecated. Please use datapointsToExclude on the monitor config block instead.




(default: false)

Metrics 🔗

The following metrics are available for this integration:

Notes 🔗

  • Learn more about the available metric types in Observability Cloud.

  • Default metrics are those metrics included in host-based subscriptions in Observability Cloud, such as host, container, or bundled metrics. Custom metrics are not provided by default and might be subject to charges. See more about metric categories.

  • To add additional metrics, see how to configure extraMetrics using the Collector.

Troubleshooting 🔗

If you are not able to see your data in Splunk Observability Cloud, try these tips:

To learn about even more support options, see Splunk Customer Success.