> 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.md).

# Operations

- [Upgrades and releases](https://docs.e6data.com/query-engine/guides/operations/upgrades-and-releases.md): How administrators choose software versions and roll out upgrades across e6data - clusters, products, and platform components.
- [Version selection and admin guide](https://docs.e6data.com/query-engine/guides/operations/upgrades-and-releases/version-selection-and-admin-guide.md): How workspace administrators select versions, refresh the available-version list, enable products, and grant upgrade permissions.
- [Product and cluster upgrades](https://docs.e6data.com/query-engine/guides/operations/upgrades-and-releases/product-and-cluster-upgrades.md): Step-by-step upgrades for each surface - a cluster's version, a product version, and a platform components release.
- [Rollbacks, failure modes, and recovery](https://docs.e6data.com/query-engine/guides/operations/upgrades-and-releases/rollbacks-failure-modes-recovery.md): How cluster and platform rollouts behave, how automatic rollback works, expected downtime, and what to do when an upgrade fails.
- [Status signals](https://docs.e6data.com/query-engine/guides/operations/upgrades-and-releases/status-signals.md): Where each upgrade surface reports progress - cluster status and Activity History, product rows, and the Platform Components section.
- [Monitoring](https://docs.e6data.com/query-engine/guides/operations/monitoring.md): Monitor cluster health, query performance, and resource utilization from the Compute Plane, and export telemetry to your own stack.
- [Health checks](https://docs.e6data.com/query-engine/guides/operations/monitoring/health-checks.md): Confirm a workspace and its clusters are healthy - what to check in the Console and, for In-VPC, in your Kubernetes cluster.
- [Metrics and alerts](https://docs.e6data.com/query-engine/guides/operations/monitoring/metrics-and-alerts.md): The metrics e6data exposes, the dashboards worth building, and the alerts to set on your observability stack.
- [Observability export](https://docs.e6data.com/query-engine/guides/operations/monitoring/observability-export.md): Export e6data telemetry to your own observability stack via OpenTelemetry - metrics, logs, and traces.


---

# 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.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.