> ## Documentation Index
> Fetch the complete documentation index at: https://docs.e6data.com/llms.txt
> Use this file to discover all available pages before exploring further.

# 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](https://docs.e6data.com/query/clusters/lifecycle-states.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](https://docs.e6data.com/query/querying/query-history.md).
* **Version upgrades.** Confirm platform components and the Metadata Service are on expected versions - see [Upgrades and releases](https://docs.e6data.com/platform/upgrades.md).

## In Your VPC deployments

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

```bash theme={"theme":{"light":"github-light","dark":"github-dark"}}
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](https://docs.e6data.com/platform/deploy/aws-cloudprem/run-first-query.md) and [Azure](https://docs.e6data.com/platform/deploy/azure-cloudprem/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](https://docs.e6data.com/platform/monitoring.md)
* [Metrics and alerts](https://docs.e6data.com/platform/monitoring/metrics-and-alerts.md)
* [Lifecycle states and error codes](https://docs.e6data.com/query/clusters/lifecycle-states.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.