---
name: watsonxdata-qhmm_querying
title: Managing diagnostic data from user interface
description: You can configure watsonx.data to store the diagnostic data such as queries history and query event-related information of the Presto engine (Presto) in a storage bucket in watsonx.data using the **Query monitoring** page. You can retrieve the history files to analyze, debug or monitor the queries from the Query workspace.
last-updated: 2025-08-26
---

> ## Documentation Index
> The table of contents for this documentation set is at https://cloud.ibm.com/docs/watsonxdata?format=markdown
> The index for all IBM Cloud docs is at: https://cloud.ibm.com/docs/llms.txt
> Use these files to discover more information as needed.

{:javascript: #javascript .ph data-hd-programlang='javascript'}
{:java: #java .ph data-hd-programlang='java'}
{:ruby: #ruby .ph data-hd-programlang='ruby'}
{:php: #php .ph data-hd-programlang='php'}
{:python: #python .ph data-hd-programlang='python'}
{:external: target="_blank" .external}
{:shortdesc: .shortdesc}
{:codeblock: .codeblock}
{:screen: .screen}
{:tip: .tip}
{:important: .important}
{:note: .note}
{:deprecated: .deprecated}
{:pre: .pre}
{:video: .video}

# Managing diagnostic data from user interface
{: #ret_qhmm}

You can configure watsonx.data to store the diagnostic data such as queries history and query event-related information of the Presto engine (Presto) in a storage bucket in watsonx.data using the **Query monitoring** page. You can retrieve the history files to analyze, debug or monitor the queries from the Query workspace.
{: shortdesc}

## Procedure
{: #ret_pr_qhmm}


1. From the navigation menu, select **Query workspace**.
1. Select the engine from **Engine** list and identify the Hive catalog that you created to store the QHMM data.
1. You can view the queries history and query event-related information of the Presto engine inside the tables within the catalog. Run queries to analyse the data.
1. The following tables are available by default:

    query_event_raw : Includes the raw data of query events in JSON format. To view the entire event data, use the following query:

    SELECT*FROM`<catalog>.<schema>`.query_event_raw;

    query_history : Includes the query History data. To view the entire Query History data, use the following query:

    SELECT*FROM`<catalog>.<schema>`.query_history;

    table_stats_information_memory : Includes the memory related information. To view the memory related information, use the following query:

    SELECT*from`<catalog>.<schema>`.table_stats_information_memory;

## Deleting QHMM schemas and tables
{: #del_qhmm}

Administrators can permanently delete the QHMM schemas and tables present in the QHMM enabled catalog by using the following CURL command :


```bash
curl --location --request DELETE '<SAAS_instance_url>/lakehouse/api/v3/<instance_id>/configuration/qhmm?engine_id=<engine_id>&catalog_name=<catalog_name>&schema_id=<schema_id>'
```
{: codeblock}

The QHMM enabled catalog must be associated to a Presto engine. If the engine is deleted or disassociated, then the catalog should be associated to next available Presto engine.
{: important}

Parameter values:

* `<SAAS_instance_url>`  : The watsonx.data access URL.
* `<instance_id>` : The unique ID for the insatnce.
* `<engine_id>` : The unique ID of the engine for which the schema and table information needs to be removed.
* `<catalog_name>` : The QHMM catalog for which the schema and table information needs to be removed.
* `<schema_id>` : The unique ID of the schema for which the table information needs to be removed.