Overview

This check collects Presto metrics, for example:

• Overall activity metrics: completed/failed queries, data input/output size, execution time.
• Performance metrics: cluster memory, input CPU, execution CPU time.

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 Presto check is included in the Datadog Agent package. No additional installation is needed on your server. Install the Agent on each Coordinator and Worker node from which you wish to collect usage and performance metrics.

Configuration

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

   This check has a limit of 350 metrics per instance. The number of returned metrics is indicated in the status page. You can specify the metrics you are interested in by editing the configuration below. To learn how to customize the metrics to collect, see the JMX Checks documentation for more detailed instructions. If you need to monitor more metrics, contact Datadog support.

2. Restart the Agent.

Metric collection

Use the default configuration of your presto.d/conf.yaml file to activate the collection of your Presto metrics. See the sample presto.d/conf.yaml for all available configuration options.

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. Add this configuration block to your presto.d/conf.yaml file to start collecting your Presto logs:

   logs:
     - type: file
       path: /var/log/presto/*.log
       source: presto
       service: "<SERVICE_NAME>"
   

   Change the path and service parameter values and configure them for your environment. See the sample presto.d/conf.yaml for all available configuration options.

3. Restart the Agent.

Validation

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

Data Collected

Metrics

Events

Presto does not include any events.

Service Checks

presto.can_connect
Returns CRITICAL if the Agent is unable to connect to and collect metrics from the monitored Presto instance, WARNING if no metrics are collected, and OK otherwise.
Statuses: ok, critical, warning

Troubleshooting

Need help? Contact Datadog support.