Ambari

Agent Check

Overview

This check monitors Ambari through the Datadog Agent.

Setup

Installation

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

Configuration

Host

Follow the instructions below to configure this check for an Agent running on a host. For containerized environments, see the Containerized section.

Metric Collection

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

   init_config:
   
   instances:
    ## @param url - string - required
    ## The URL of the Ambari Server, include http:// or https://
    #
    - url: localhost

2. Restart the Agent.

Log collection

Available for Agent versions >6.0

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

   logs_enabled: true

2. Edit your ambari.d/conf.yaml by uncommenting the logs lines at the bottom. Update the logs path with the correct path to your Ambari log files.

     logs:
       - type: file
         path: /var/log/ambari-server/ambari-alerts.log
         source: ambari
         service: ambari
         log_processing_rules:
             - type: multi_line
               name: new_log_start_with_date
               # 2019-04-22 15:47:00,999
               pattern: \d{4}\-(0?[1-9]|1[012])\-(0?[1-9]|[12][0-9]|3[01])
     ...

3. Restart the Agent.

Containerized

For containerized environments, see the Autodiscovery Integration Templates for guidance on applying the parameters below.

Metric collection

Log collection

Available for Agent versions >6.0

Collecting logs is disabled by default in the Datadog Agent. To enable it, see Docker log collection.

Validation

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

Data Collected

This integration collects for every host in every cluster the following system metrics:

• boottime
• cpu
• disk
• memory
• load
• network
• process

If service metrics collection is enabled with collect_service_metrics this integration collects for each whitelisted service component the metrics with headers in the white list.

Metrics

Service Checks

ambari.can_connect:
Returns OK if the cluster is reachable, otherwise returns CRITICAL.

ambari.state:
Returns OK if the service is installed or running, WARNING if the service is stopping or uninstalling, or CRITICAL if the service is uninstalled or stopped.

Events

Ambari does not include any events.

Troubleshooting

Need help? Contact Datadog support.