Overview

This check monitors Impala through the Datadog Agent.

Setup

Follow the instructions below to install and configure this check for an Agent running on a host. For containerized environments, see the Autodiscovery Integration Templates for guidance on applying these instructions.

Installation

The Impala check is included in the Datadog Agent package. No additional installation is needed on your server.

Configuration

1. Edit the impala.d/conf.yaml file, in the conf.d/ folder at the root of your Agent’s configuration directory to start collecting your Impala performance data. See the sample impala.d/conf.yaml for all available configuration options.

Here is an example monitoring a daemon:

init_config:
   
instances:
  ## @param service_type - string - required
  ## The Impala service you want to monitor. Possible values are `daemon`, `statestore`, and `catalog`.
  #
- service_type: daemon

  ## @param openmetrics_endpoint - string - required
  ## The URL exposing metrics in the OpenMetrics format.
  ##
  ## The default port for the services are:
  ## - Daemon: 25000
  ## - Statestore: 25010
  ## - Catalog: 25020
  #
  openmetrics_endpoint: http://%%host%%:25000/metrics_prometheus

You can also monitor several services at the same time with the same agent:

init_config:
   
instances:

- service_type: daemon
  service: daemon-1
  openmetrics_endpoint: http://<DAEMON-1-IP>:25000/metrics_prometheus
- service_type: daemon
  service: daemon-2
  openmetrics_endpoint: http://<DAEMON-2-IP>:25000/metrics_prometheus
- service_type: statestore
  openmetrics_endpoint: http://<STATESTORE-IP>:25010/metrics_prometheus
- service_type: catalog
  openmetrics_endpoint: http://<CATALOG-IP>:25020/metrics_prometheus

2. Restart the Agent.

Validation

Run the Agent’s status subcommand and look for impala under the Checks section.

Data Collected

Metrics

Events

The Impala integration does not include any events.

Service Checks

impala.daemon.openmetrics.health
Returns CRITICAL if the check cannot access the Prometheus metrics endpoint of the Impala daemon instance.
Statuses: ok, critical

impala.statestore.openmetrics.health
Returns CRITICAL if the check cannot access the Prometheus metrics endpoint of the Impala statestore instance.
Statuses: ok, critical

impala.catalog.openmetrics.health
Returns CRITICAL if the check cannot access the Prometheus metrics endpoint of the Impala catalog instance.
Statuses: ok, critical

Logs

The Impala integration can collect logs from the Impala services and forward them to Datadog.

1. Collecting logs is disabled by default in the Datadog Agent. Enable it in your datadog.yaml file:

   logs_enabled: true
   

2. Uncomment and edit the logs configuration block in your impalad.d/conf.yaml file. Here’s an example with the daemon process:

   logs:
     - type: file
       path: /var/log/impala/impalad.INFO
       source: impala
       tags:
       - service_type:daemon
       log_processing_rules:
       - type: multi_line
         pattern: ^[IWEF]\d{4} (\d{2}:){2}\d{2}
         name: new_log_start_with_log_level_and_date
     - type: file
       path: /var/log/impala/impalad.WARNING
       source: impala
       tags:
       - service_type:daemon
       log_processing_rules:
       - type: multi_line
         pattern: ^[IWEF]\d{4} (\d{2}:){2}\d{2}
         name: new_log_start_with_log_level_and_date
     - type: file
       path: /var/log/impala/impalad.ERROR
       source: impala
       tags:
       - service_type:daemon
       log_processing_rules:
       - type: multi_line
         pattern: ^[IWEF]\d{4} (\d{2}:){2}\d{2}
         name: new_log_start_with_log_level_and_date
     - type: file
       path: /var/log/impala/impalad.FATAL
       source: impala
       tags:
       - service_type:daemon
       log_processing_rules:
       - type: multi_line
         pattern: ^[IWEF]\d{4} (\d{2}:){2}\d{2}
         name: new_log_start_with_log_level_and_date
   

See the example configuration file on how to collect all logs.

Troubleshooting

Need help? Contact Datadog support.