> For the complete documentation index, see [llms.txt](https://v2.dataos.info/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://v2.dataos.info/operate/tenant-admin/monitoring.md).

# Monitoring

As a Tenant Admin, you monitor the Tenant Resources that teams depend on, including Compute, runtime services, Stacks, Data Product workloads, Secrets, and Depots. Your goal is to confirm that the Tenant is healthy and has enough capacity for teams to build and run Data Product workloads.

## What to watch

* **Compute:** Check whether Tenant Computes are active and whether Data Product workloads are scheduling on them. A Data Product workload stuck in Pending usually means no nodes match the Compute's nodeSelector, or the Compute pool does not have enough capacity.
* **Stack:** Check whether the execution Stacks used by Tenant Data Product workloads, such as Vulcan is healthy. If a Stack is unhealthy, Data Product workloads that depend on it may fail or stop progressing.
* **Resources:** Review the Resources in the Tenant, such as Secrets, Depots, Computes, and Data Product workloads. Keep ownership clear so orphaned, unused, or failing Resources can be handled quickly.

## How to monitor

Check Compute health and whether Data Product workloads are scheduling on it:

```bash
# List all computes in the tenant
dataos-ctl resource get -t compute

# Detailed status of one compute, including scheduling messages
dataos-ctl resource get -t compute -n <name> -d
```

Check Tenant Resources and ownership:

```bash
# All resources of a type, with owners
dataos-ctl resource get -t depot
dataos-ctl resource get -t secret

# Everything you own, or across the tenant
dataos-ctl resource get -t workflow -a
```

A Resource is healthy when `get` reports it as `active` with no errors.

For a Data Product workload stuck in `Pending`, inspect the detailed status for the scheduling reason and confirm a Compute matches its `nodeSelector`.

## Monitoring practices

* **Capacity check before onboarding.** Before adding a team or a heavy Data Product workload, confirm that the Tenant has enough compute capacity. If capacity is not enough, add or request additional Compute (see [Create Compute](/operate/tenant-admin/create-compute.md)).
* **Check Compute and Stack health.** If a developer reports Data Product workload failures, first check whether Tenant Compute and the required Stacks are healthy. If Tenant Resources are healthy, direct the developer to their product runs and logs (see [Operate your product](/operate/data-developer/operate-your-product.md) in the Developer section). If the whole Tenant looks down, escalate to the Operator. Their [Monitoring](/operate/dataos-operator/monitoring.md) covers the Data Plane.
* **Review shared access regularly.** Periodically review who has the `Can Use` on shared Compute and data sources, and revoke what is no longer needed (see [Manage access](/operate/tenant-admin/governance.md)).

Instance and Data Plane health sit above you (the Operator's [Monitoring](/operate/dataos-operator/monitoring.md)); individual product health sits below you (the Developer's [Operate your product](/operate/data-developer/operate-your-product.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://v2.dataos.info/operate/tenant-admin/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.