Configure Query Spotlight: Presto/Trino (RPM/DEB)

Query Spotlight support for Presto/Trino queries is in Technical Preview, and we welcome your feedback.

On This Page

Prerequisites
Enable Fetching of Presto/Trino Query Data

Prerequisites

Before you begin configuring Query Spotlight for Presto/Trino query monitoring, ensure that your system meets the required prerequisites.

Pepperdata must be installed on the host(s) to be configured for Query Spotlight.
Your cluster uses a supported combination of Presto/Trino version and platform; see the entries for Query Spotlight 7.1.x in the table of Supported Presto/Trino-Distro Combinations by Query Spotlight Version.

Enable Fetching of Presto/Trino Query Data

To enable Pepperdata to fetch Presto/Trino query data, add the required variables to the Pepperdata configuration.

Procedure

Important: You can begin with any coordinator host, but be sure to repeat all the procedure steps on every coordinator host.

On any coordinator—a host on which the Presto/Trino coordinator configuration value is true and the REST server is running—open the host’s Pepperdata site file, pepperdata-site.xml, for editing.

By default, the Pepperdata site file, pepperdata-site.xml, is located in /etc/pepperdata. If you customized the location, the file is specified by the PD_CONF_DIR environment variable. See Change the Location of pepperdata-site.xml for details.
Add the property to enable fetching the data.
```
<property>
  <name>pepperdata.agent.genericJsonFetch.presto.enabled</name>
  <value>true</value>
</property>
```
Malformed XML files can cause operational errors that can be difficult to debug. To prevent such errors, we recommend that you use a linter, such as xmllint, after you edit any .xml configuration file.

(Non-Default environments) If your environment does not match the defaults that are assumed by Pepperdata, add/edit any of the configuration properties that should be different from their default values, in accordance with your system/environment. For example, you can change the authentication type (pepperdata.agent.genericJsonFetch.presto.http.authentication.type) from simple to BASIC.

The table shows the defaults that are assumed.

Property Name	Default Value
`pepperdata.agent.genericJsonFetch.presto.interval`	`5000`
`pepperdata.agent.genericJsonFetch.presto.port`	`8080`
`pepperdata.agent.genericJsonFetch.presto.httpsEnabled`	`false`
`pepperdata.agent.genericJsonFetch.presto.http.authentication.type`	`simple`
`pepperdata.agent.genericJsonFetch.presto.auth.username`	`""` [an empty string, including the quote marks]
`pepperdata.agent.genericJsonFetch.presto.auth.password`	`""` [an empty string, including the quote marks]
`pepperdata.agent.genericJsonFetch.presto.auth.password_file`	`""` [an empty string, including the quote marks]
`pepperdata.agent.genericJsonFetch.presto.auth.encr_password`	`""` [an empty string, including the quote marks]
`pepperdata.agent.genericJsonFetch.presto.auth.encr_password_file`	`""` [an empty string, including the quote marks]
`pepperdata.agent.genericJsonFetch.presto.path`	`"/v1/query"`
`pepperdata.agent.genericJsonFetch.presto.maxSizeBytes`	`2000000`
`pepperdata.agent.genericJsonFetch.presto.https.enabled.protocols`	`TLSv1`

Save your changes and close the file.
Restart the PepAgent.

You can use either the service (if provided by your OS) or systemctl command:
- sudo service pepagentd restart
- sudo systemctl restart pepagentd
If any of the process’s startup checks fail, an explanatory message appears and the process does not start. Address the issues and try again to start the process.
Repeat steps 1–5 on every coordinator host in your cluster.

Important: Be sure to repeat steps 1–5 on every coordinator host. If you skip the configuration process on a coordinator host, Pepperdata is unable to collect metrics for queries that run on that host.
Contact Pepperdata Support to request that Presto/Trino query monitoring be activated for your Pepperdata dashboard.