This check monitors Ambari through the Datadog Agent.
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.
The Ambari check is included in the Datadog Agent package. No additional installation is needed on your server.
-
Edit the
ambari.d/conf.yaml
file, in theconf.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.
Available for Agent >6.0
-
Collecting logs is disabled by default in the Datadog Agent, enable it in your
datadog.yaml
file:logs_enabled: true
-
Edit your
ambari.d/conf.yaml
by uncommenting thelogs
lines at the bottom. Update the logspath
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 pattern: \d{4}\-(0?[1-9]|1[012])\-(0?[1-9]|[12][0-9]|3[01]) # 2019-04-22 15:47:00,999 ...
Run the Agent's status subcommand and look for ambari
under the Checks section.
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.
See metadata.csv for a list of all metrics provided by this integration.
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. For a complete enumeration, see this file.
Ambari does not include any events.
Need help? Contact Datadog support.