HAProxy load balancer discovery with probes

  • Release version: Washingtondc
  • Updated February 1, 2024
  • 2 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of HAProxy Load Balancer Discovery with Probes

    HAProxy load balancer discovery utilizes SSH for identifying HAProxy Community edition load balancers. As of version 1.15.0, pattern-based discovery is the default method, though probe-based discovery can still be enabled.

    Show full answer Show less

    Key Features

    • Discovery Requirements: Ensure HAProxy software is installed on a Linux server with the MID Server deployed and having access to the HAProxy configuration file.
    • Probe Operations: The configuration probe checks for the 'haproxy.cfg' file through specified methods.
    • Process Identification: Discovery uses the Unix - Active Processes probe to identify running HAProxy processes by their name.
    • Probes Triggered:
      • HAProxy – Version: Gathers and records the HAProxy version.
      • HAProxy – Get Configuration: Collects and populates additional details in various Load Balancer-related tables.

    Key Outcomes

    Upon successful discovery, records are created in the HAProxy Load Balancers table, along with related records in other configuration item (CI) tables, establishing relationships among load balancer services, pools, and members.

    Discovery of HAProxy Community edition load balancers is performed by SSH.

    Note:
    Starting with Discovery and Service Mapping Patterns 1.15.0 version, pattern-based discovery is the default method for discovering HAProxy load balancers.

    HAProxy is an open-source load balancer that can manage any TCP service. It is particularly suited for HTTP load balancing because it supports session persistence and Layer 7 processing. Discovery supports HAProxy for HTTP load balancing. TCP load-balancing is not supported.

    Consider the following requirements for discovering the HAProxy:
    • The HAProxy software is installed and running on a Linux server.
    • The MID Server is deployed to explore the server and the MID Server has access to the server HAProxy configuration file.
    • The configuration probe checks for the haproxy.cfg file using one of the following methods:
      • Using the f parameter for the HAProxy process output.
      • Using the default /etc/haproxy/haproxy.cfg path.
    • The HAProxy probes require credentials and execute privileges to run commands.

    Discovery uses the Unix - Active Processes probe to identify an HAProxy load balancer when the name of the process is haproxy. If this criterion matches, a record is created in the HAProxy Load Balancers [cmdb_ci_lb_haproxy] table if one does not already exist for that running process.

    The following probes are triggered after classification:
    Table 1. HAProxy probes
    Probe Description Commands
    HAProxy – Version The sensor of this probe populates the HAProxy version in the HAProxy Load Balancers [cmdb_ci_lb_haproxy] table. haproxy
    HAProxy – Get Configuration The sensor of this probe populates additional information in the HAProxy Load Balancers [cmdb_ci_lb_haproxy] table. The probe also populates information in the Load Balancer Service [cmdb_ci_lb_service], Load Balancer Pool [cmdb_ci_lb_pool], Load Balancer Pool Member [cmdb_ci_lb_pool_member], Load Balancer Interface [cmdb_ci_lb_interface], and Load Balancer Application [cmdb_ci_lb_appl] tables. echo, sed, cut, grep, egrep (within the Borne shell script)

    In addition to populating the data, the following relationships records are created in CI Relationships [cmdb_rel_ci] table:

    • The records in the cmdb_ci_lb_appl table run on the cmdb_ci_web_server table records.
    • The records in the cmdb_ci_lb_service table use the cmdb_ci_lb_pool table records.
    • The records in the cmdb_ci_pool table are used by the cmdb_ci_service table records.
    • The records in the cmdb_ci_pool table are members of the cmdb_ci_pool_member table records.
    • The records in the cmdb_ci_pool_member table are members of the cmdb_ci_pool table records.