Configure the Datadog Polling LAM

The Datadog Polling LAM has been validated with Datadog v2018. Before you set up the LAM, ensure you have met the following requirements for each Datadog server:

Edit the configuration file to control the behavior of the Datadog Polling LAM. You can find the file at $MOOGSOFT_HOME/config/datadog_client_lam.conf

See the Datadog Polling LAM Reference and LAM and Integration Reference for a full description of all properties. Some properties in the file are commented out by default. Uncomment properties to enable them.

You can configure the Datadog LAM to retrieve events from one or more targets. The following example demonstrates a configuration that targets two Datadog sources. For a single source, comment out the target2 section. If you have more than two sources, add a target section for each one and uncomment properties to enable them.

In the following example, the Datadog LAM is configured to poll two different Datadog instances. The LAM uses the tokens NodeID and EventID to identify duplicate events. These configurations specify use variables $from and $to for the query time window; the LAM specifies UNIX epoch values for these fields when it sends a poll request.

monitor:
{
    name: "Datadog REST Client Monitor",
    class: "CRestClientMonitor",
    request_interval: 60,
    targets:
    {
        target1:
        {
            url: "https://instance1.datadoghq.com/api/v1/events",
            proxy:
            {
                host: "localhost",
                port: 8181,
                user: "user",
                password: "pass",
                #encrypted_password: "ieytOFRUdLpZx53nijEw0rOh07VEr8w9lBxdCc7229o="
            },
            request_interval: 60,
            timeout: 120
            disable_certificate_validation: false,
            path_to_ssl_files: "config",
            server_cert_filename: "server.crt",
            client_key_filename: "client.key",
            client_cert_filename: "client.crt",
            requests_overlap: 10,
            enable_epoch_converter: true,
            results_path: "events",
            overlap_identity_fields: [ "NodeID", "EventID" ],
            request_query_params:  
            {  
                start: "$from",
                end: "$to",
                api_key: "1234",
                application_key: "1234"
            },
            params_date_format: "%s"
        }
        target2:
        {
            url: "https://instance2.datadoghq.com/api/v1/events",
            user: "user2",
            host: "localhost",
            port: 8181,
            request_interval: 60,
            timeout: 120
            disable_certificate_validation: false,
            path_to_ssl_files: "config",
            server_cert_filename: "server.crt",
            client_key_filename: "client.key",
            client_cert_filename: "client.crt",
            path_to_ssl_files: "config",
            requests_overlap: 10,
            enable_epoch_converter: true,
            results_path: "events",
            overlap_identity_fields: [ "NodeID", "EventID" ],
            request_query_params:  
            {  
                start: "$from",
                end: "$to",
                api_key: "1234",
                application_key: "1234"
            },
            params_date_format: "%s",
        }
    }    
},
agent:
{
    name: "Datadog Client",
    capture_log: "$MOOGSOFT_HOME/log/data-capture/datadog_client_lam.log"
},
log_config:
{
    configuration_file: "$MOOGSOFT_HOME/config/logging/datadog_client_lam_log.json"
},

Configure the Datadog LAM for high availability if required. See High Availability Overview for details.

The Datadog Polling LAMbot processes and filters events before sending them to the Message Bus. You can customize or bypass this processing if required. You can also load JavaScript files into the LAMbot and execute them.

See LAMbot Configuration for more information. An example Datadog Polling LAM filter configuration is shown below.

filter: 
{
    presend: "DatadogClientLam.js",
    modules: [ "CommonUtils.js" ]
}

You can configure custom mappings in the Datadog Polling LAMbot. See Tokenize Source Event Data information for details.

By default, the following DataDog event properties map to the following Moogsoft Enterprise Datadog Polling LAM properties:

The overflow properties are mapped to "custom info" and appear under custom_info in Moogsoft Enterprise alerts. This mapping requires Event Monitor tag values in the correct format ({{event.tags.example-tag}}) as described in the Datadog documentation.

Restart the Datadog LAM to activate any changes you make to the configuration file or LAMbot.

The LAM service name is datadogclientlamd.

See Control Moogsoft Enterprise Processesfor further details.

If the LAM fails to connect to one or more Datadog sources, Moogsoft Enterprise creates an alert and writes the details to the process log. Refer to the logging details for LAMs and integrations for more information.