Configure Query Spotlight: Presto/Trino (Cloud)

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

On This Page

Prerequisites
Procedure: 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.

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.

Procedure: Enable Fetching of Presto/Trino Query Data

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

From the environment’s cluster configuration folder (in the cloud), download the Pepperdata site file, /etc/pepperdata/pepperdata-site.xml, to a location where you can edit it.
Open the file for editing, and 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.

Configure the username and password for accessing the Presto/Trino server.

For Amazon EMR, typically the username is hadoop.
Be sure to replace the your-username and your-password placeholders with your actual username and password, respectively.

<property>
  <name>pepperdata.agent.genericJsonFetch.presto.auth.username</name>
  <value>"your-username"</value>
</property>
<property>
  <name>pepperdata.agent.genericJsonFetch.presto.auth.password</name>
  <value>"your-password"</value>
</property>

(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.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.
Upload the revised file to overwrite the original pepperdata-site.xml file.