> 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/health-checks.md).

# Health checks

Confirm a workspace and its clusters are healthy - what to check in the Console and, for In-VPC, in your Kubernetes cluster.

Use these checks to confirm a workspace and its clusters are healthy, whether after a change or as a routine review.

## In the Console

* **Cluster status.** The Clusters list shows each cluster's state - `Running`, `Suspended`, `Pending`, `Error`, or `Degraded`. A healthy cluster is `Running` (or intentionally `Suspended`). Hover over an `Error` state for the reason; see [Lifecycle states and error codes](/query-engine/guides/clusters/lifecycle-states-and-error-codes.md).
* **Activity history.** Each cluster's recent lifecycle events (create, resume, suspend, update, scale) with outcomes - the first stop when something looks off.
* **Run History.** A spike in failed or timed-out queries is an early signal. Filter by status to spot patterns; see [Query history](/query-engine/guides/querying/query-history-and-saved-queries.md).
* **Version upgrades.** Confirm platform components and the Metadata Service are on expected versions - see [Upgrades and releases](/query-engine/guides/operations/upgrades-and-releases.md).

## In Your VPC deployments

For In-VPC deployments, also confirm the workspace pods and platform components are running in your Kubernetes cluster:

```bash
kubectl get pods -n <WORKSPACE_NAME>
kubectl get pods -n e6operator
```

Expected workspace pods include `console`, `envoy`, `xds`, and the metadata services. See the In-VPC run-first-query checks for [AWS](/query-engine/guides/deployment/aws-in-vpc/run-first-query.md) and [Azure](/query-engine/guides/deployment/azure-in-vpc/run-first-query.md).

## What healthy looks like

* Clusters are `Running` or intentionally `Suspended`; none stuck in `Pending`, `Error`, or `Degraded`.
* Failed-query and timeout rates are within your normal baseline.
* Suspended clusters resume on the first query.

## See also

* [Monitoring](/query-engine/guides/operations/monitoring.md)
* [Metrics and alerts](/query-engine/guides/operations/monitoring/metrics-and-alerts.md)
* [Lifecycle states and error codes](/query-engine/guides/clusters/lifecycle-states-and-error-codes.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/health-checks.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.