Installation Guide
Pulse 4.x.x
Overview
Prerequisites
Installation
Advanced Installation
Admin UI (K8S only)
Pulse Administration
Upgrade
Advanced Feature Integrations
Developer Tools
Troubleshooting
Title
Message
Create new category
What is the title of your new category?
Edit page index title
What is the title of the page index?
Edit category
What is the new title of your category?
Edit link
What is the new title and URL of your link?
Configure ODP Trino
Summarize Page
Copy Markdown
Open in ChatGPT
Open in Claude
Connect to Cursor
Connect to VS Code
This page helps you enable Trino JMX and configure the Pulse event listener so Pulse can collect metrics and display Trino query statistics.
- Pulse hook JARs are included in the installation package.
- To enable query statistics in Pulse, configure the Trino event listener.
- Trino’s event listener framework allows custom plugins to respond to query lifecycle events for advanced logging, debugging, and performance monitoring.
- The supported events are query creation and query completion.
- Each event provides session details, execution metrics, resource usage, and timelines.
Trino versions 472 and 435 support the hook jar.
Enable Trino JMX
In the Ambari UI:
- Navigate to Trino > Configs >
Advanced config-properties. - In
Coordinator Node ConfigandWorker Node Config, add the following parameters at the end of the file:
Bash
jmx.rmiregistry.port=9980jmx.rmiserver.port=9981Place Trino Hook JAR
- In the Trino node, navigate to the Trino plugin folder.
In the folder:
Bash
/usr/odp/current/trino/plugin/- Create the event listener directory.
Create the following directory:
Bash
ad-trino-event-listener/- Place the Trino Hook JAR in the directory.
Hook JAR:
Bash
ad-trino-event-listener-1.0.jar.In the directory:
Bash
ad-trino-event-listener/- Create the
event-listener.propertiesfile.
If not already present, create the file in the directory:
Bash
/usr/odp/current/trino/conf/- Add the following properties.
In the event-listener.properties file, add the properties:
Bash
event-listener.name=ad-trino-event-listenerad.cluster=<your-cluster-name>ad.events.streaming.servers=<Pulse-IP>:19009Replace <your-cluster-name> and <Pulse-IP> with actual values from your environment.
- Configure the plugin directory path.
If not already set, add the following line:
Bash
plugin.dir=/usr/odp/current/trino/pluginTo the node.properties file:
Bash
/usr/odp/current/trino/conf/node.properties- Restart the Trino coordinator server.
All configurations must be applied to the Trino coordinator server.
Result
- Trino exposes JMX metrics on the configured port.
- Trino hook emits execution events to Pulse.
Type to search, ESC to discard
Type to search, ESC to discard
Type to search, ESC to discard
Last updated on
Was this page helpful?
Next to read:
Configure ODP RangerFor additional help, contact www.acceldata.force.com OR call our service desk +1 844 9433282
Copyright © 2026
Discard Changes
Do you want to discard your current changes and overwrite with the template?
Archive Synced Block
Message
Create new Template
What is this template's title?
Delete Template
Message