Adding telemetry diagnostic tools through the user interface

This topic provides the procedure to add telemetry diagnostic tools for your Presto (Java) engine through the user interface of IBM® watsonx.data.

Before you begin

Ensure you have access to the watsonx.data console and credentials for the telemetry tools (Instana or Prometheus).

The Instana or Prometheus tool must be installed following the instruction provided below based on requirement:

Log in to the watsonx.data console.
From the navigation menu, select Configurations, and click OpenTelemetry.
In the OpenTelemetry page, click Diagnostic +.

In the Add telemetry diagnostic window, enter the following details:

Add telemetry diagnostic details
Field	Description
Available Telemetry Tools	Select the telemetry diagnostic tool (Instana, Prometheus) from the list.
Telemetry Endpoint	Enter the endpoint URL of the selected tool. Format: `http://<host>:<port>/<path>` or `https://<host>:<port>/<path>`. Use port `4317` for OTLP over GRPC and `4318` for OTLP over HTTP.
Host Name	If the selected telemetry tool is Instana, enter the host ID of the tool. See Configuring the resource attributes.
Password	Enter the Instana agent key or Prometheus password.
Connection status	Click Test connection to validate the endpoint and credentials.
Associated diagnostics	Select the checkbox to associate a diagnostic type (logs, metrics, traces) to the telemetry tool.

Currently Instana provides only metrics and traces diagnostic data. Prometheus provides only metrics diagnostic data.

Click Add to apply the telemetry tool integration.

The user may need to wait for a short time until the pods restart.
Access and review the diagnostics list of metrics for engines supported in your instance by using the drop-down menu to:
- Enable: Activate the diagnostic.
- Disable: Pause data collection.
- Edit: Update configuration details.
- View Details: Inspect current setup.
- Disassociate: Remove the diagnostic from the engine.
Once all supported diagnostic types have been successfully associated with any one or both telemetry tools, the Add Diagnostic button is disabled.

To configure a new diagnostic tool or switch to another, you must either:
- Edit the existing configuration.
- Disable the current diagnostic.
- Disassociate it.

To review diagnostic telemetry (including internal and synthetic calls):

Log in to the Instana UI.
Navigate to Analytics → Applications → Calls.
In the left-side panel, locate the Hidden calls section.
Enable the following options:
- Show synthetic calls
- Show internal calls

This ensures that all internal, system-generated, and synthetic call data relevant to diagnostics is visible in the UI.

Go to Analytics → Applications → Calls.
Select Add filter.
In the filter search bar, type OpenTelemetry → Custom → crn.
Choose the crn attribute and set it to the desired <crn_value>.
Adjust the retention window to focus on recent trace activity:
- Last 5 minutes
- Last 10 minutes
- Last 30 minutes

These retention periods help ensure recent query execution traces are visible without noise from older calls.

Log in to the Instana UI and navigate to Analyze Infrastructure.
In the data source selector, choose OpenTelemetry to view all OpenTelemetry resources.
Click Add filter, select OpenTelemetry Resource → otel.attribute → k8s.namespace.name. Enter the required watsonx.data instance namespace to filter the view.
From the filtered results, select the endpoint metric-scraper-presto associated with your instance.
Use Select metrics to browse all available OpenTelemetry metrics exposed by the Presto metric scraper.
Choose any metric to open its live time-series visualization, where you can analyze current values, trends, and attributes.

Access the Prometheus UI for your environment.
In the Expression field, begin typing the metric name (for example, presto_).
Prometheus will automatically display all metrics collected from metric-scraper-presto.
Select the required metric and click Execute to view the result.