# Cluster status and metrics

[Weaviate Cloud (WCD)](/go/console?utm_content=cloud) exposes two ways of checking the cluster status:

- A **[web interface](#select-a-cluster)** in the Weaviate Cloud console.
- An **[API endpoint](#api-endpoint)** that provides information about your Weaviate instance.

## Select a cluster

[Embedded content embed](https://app.guideflow.com/embed/qp7x9q6fjr)

:::accordion{title="Select your cluster"}
1. Open the [Weaviate Cloud console](/go/console?utm_content=cloud).
2. Open the `Clusters` list from the left sidebar.
3. Select the cluster you want to inspect.
4. The cluster details panel will open to the right.
:::

## Cluster metrics

Depending on the data available for your cluster, the following metrics dashboards are available:

- `Query Latency`
- `Ingestion Throughput`
- `Average Batch Size`
- `Object Count`

[Embedded content embed](https://app.guideflow.com/embed/zkj3n21hep)

:::accordion{title="Explore cluster metrics"}
1. Open the [Weaviate Cloud console](/go/console?utm_content=cloud).
2. Select the cluster you want to inspect from the left sidebar.
3. Locate the cluster `Metrics` section on the `Cluster details` page.
4. Click the `View all Metrics` button to find all the available metrics for your cluster.
:::

## Cluster status information

You can see the following cluster statistics at the top of the page:

- `Dimensions stored`
- `Object count`
- `Cluster expires on` (only for free clusters, based on inactivity)

You can find the following information on the cluster details page:

- `Name of the cluster`
- `REST Endpoint`
- `gRPC Endpoint`
- `API Keys`
- `Roles`
- `Weaviate Database version`
- `Cloud provider`
- `Cloud region`
- `Created at`
- `Type` (Shared Cloud or Free)
- `Backup retention days` (only for Shared Cloud cluster)
- `Availability SLA` (only for Shared Cloud cluster)

Clusters also have an `Advanced configuration` section to configure or check the status of these additional settings:

- `Enable auto schema generation`
- `Allow all CORS origins`
- `Enable MCP Read-Only` (see [Weaviate MCP server](../ai-assisted-vibe-coding/configuration-mcp-server.md#weaviate-cloud). The MCP server itself is always enabled, and changes apply without a restart)

## API Endpoint

To get cluster details programmatically, use the [`nodes`](../monitoring-and-logging/status.md#cluster-node-data) REST endpoint.

The `nodes` endpoint returns an array of nodes. The nodes have the following fields:

- `name`: Name of the node.
- `status`: Status of the node (one of: `HEALTHY`, `UNHEALTHY`, `UNAVAILABLE`, `INDEXING`).
- `version`: Version of Weaviate running on the node.
- `gitHash`: Short git hash of the latest commit of Weaviate running on the node.
- `stats`: Statistics for the node.
  - `shardCount`: Total number of shards on the node.
  - `objectCount` Total number of indexed objects on the node.
- `shards`: Array of shard statistics. To see `shards` details, set `output == verbose`.
  - `name`: Name of the shard.
  - `class`: Name of the collection stored on the shard.
  - `objectCount`: Number of indexed objects on the shard.
  - `vectorQueueLength`: Number of objects waiting to be indexed on the shard. (Available starting in Weaviate `1.22` when `ASYNC_INDEXING` is enabled.)

## Enabled modules

Each Weaviate instance has a set of enabled modules. This list will vary depending on the instance, due to the Weaviate version and Weaviate Cloud policies.

To see the list of enabled modules on a Weaviate Cloud instance:

- Open the Weaviate Cloud console.

- Click on `Clusters` and select the cluster you want to check.

- Scroll to the `Available modules` section under
  `Advanced options`.

- You can click on a module to open its documentation.

![Create a cluster](/assets/docs/cloud/img/weaviate-cloud-available-modules.png)

Available modules for your cluster.

## Support

If you use **Weaviate Cloud** (Database cluster(s) or Weaviate product in the cloud) or have a self-hosted support package, open a ticket in the [Support Portal](https://support.weaviate.io) or email [Weaviate support](mailto\:support@weaviate.io) directly. To add a [support plan](https://weaviate.io/support-plans), contact [Weaviate sales](https://weaviate.io/pricing#contact-sales).

Use the **Support Portal** for direct help from the Weaviate team: open and track tickets, and we'll respond in line with your support plan. The **Community Forum** is open to everyone, and a great place to ask questions, get help with your cluster, and connect with other developers. For all the ways to get help, see the [Support overview](../support/overview.md).

::::card-grid
:::card{title="Weaviate Support Portal" href="https://support.weaviate.io" icon="headset"}
Direct help from the Weaviate team for Weaviate Cloud. Open and track tickets in the **Support Portal**.
:::

:::card{title="Weaviate Community Forum" href="https://forum.weaviate.io/c/support" icon="messages-square"}
Ask questions, share ideas, and connect with other developers on our **Community forum**.
:::
::::

## Related pages

- [Agents](./agents-index.md)
- [AI-assisted Weaviate code generation](./ai-assisted-vibe-coding-index.md)
- [APIs](./apis-index.md)
- [Authorization and authentication](./authorization-and-authentication-index.md)
- [Benchmarks](./benchmarks-index.md)
- [Best practices](./best-practices-index.md)
- [Client libraries](./clients-index.md)
- [Client Libraries / SDKs](./client-libraries-index.md)
- [Cloud](./cloud-index.md)
- [Cloud account management](./cloud-account-management-index.md)

# Agent Instructions

This portal answers questions programmatically. To receive a synthesized,
source-cited answer instead of crawling page by page, append the `?ask=`
query parameter to any page URL on this site:

    /guides/quickstart?ask=how+do+I+authenticate

Optional parameters:

- `&goal=<what-you-are-trying-to-do>` steers the answer toward your
  objective (e.g. `&goal=write+a+python+client`).
- `&version=<label>` scopes the answer to a mounted version when the
  portal publishes more than one.

The response is `text/markdown`: the answer followed by a `# Sources` list
of the portal pages it was grounded in. Status codes are the contract:

- `200` — the answer; `402` — the portal owner’s plan or answer credits are
  exhausted (surface this to your operator; do NOT retry); `429` — you are
  rate-limited; back off for the `Retry-After` seconds; `503` — the answer
  lane is temporarily unavailable; fall back to crawling the `.md` pages.

For the full corpus map read `llms.txt` at the site root; for the tool
surface (search + page fetch as MCP tools) see `/mcp`.
