> For the complete documentation index, see [llms.txt](https://docs.e6data.com/query-engine/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.e6data.com/query-engine/guides/operations/monitoring.md).

# Monitoring

Monitor cluster health, query performance, and resource utilization from the Compute Plane, and export telemetry to your own stack.

e6data surfaces real-time cluster status and per-query metrics in the Compute Plane, and can export telemetry to your own observability stack. This page covers what you can see in-product; for exporting to external tools, see [Observability export](/query-engine/guides/operations/monitoring/observability-export.md).

## Cluster status

The Clusters list shows each cluster's current state:

| Status        | Meaning                                            |
| ------------- | -------------------------------------------------- |
| **Active**    | Cluster is running and serving queries             |
| **Suspended** | Cluster is suspended (no compute, no cost)         |
| **Pending**   | Cluster is being created or resumed; not yet ready |
| **Error**     | A problem prevented the cluster from starting      |

Hover over an Error status to see the underlying message. For specific error codes, see [Cluster errors](/query-engine/reference/error-codes/cluster.md).

## Cluster details

Click a cluster to see its connection info (endpoints, port, credentials reference - see [Create and manage clusters](/query-engine/guides/clusters/create-and-manage-clusters.md)), active queries, resource usage (executor count, CPU, memory), and recent activity.

## Query metrics

Open **Run History** to see metrics per query - execution time, bytes scanned, rows returned, cluster used, and the user and access method (UI, JDBC, REST, and so on). Filter by user, cluster, status, or time range. See [Query history and saved queries](/query-engine/guides/querying/query-history-and-saved-queries.md).

## Alerting

Common alerts to set up in your observability stack:

| Alert                    | Threshold                                                  |
| ------------------------ | ---------------------------------------------------------- |
| Cluster fails to resume  | More than 5 minutes in Pending after a resume is triggered |
| Query timeout rate spike | Sudden increase in timed-out queries                       |
| Concurrent query backlog | Queries queued longer than expected                        |
| Failed query rate        | Above a baseline you've established for the cluster        |

## See also

* [Observability export](/query-engine/guides/operations/monitoring/observability-export.md) - export metrics, logs, and traces via OpenTelemetry.
* [Query history and saved queries](/query-engine/guides/querying/query-history-and-saved-queries.md)
* [Cluster errors](/query-engine/reference/error-codes/cluster.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.e6data.com/query-engine/guides/operations/monitoring.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.