# monitoring:read

Last edited on 28 Aug 2025

## Scope Summary

View Monitoring metrics and alert policies

## Required Scopes

To add a scope to an API token, you must also add its required scopes. For example, to add a non-read scope for a resource type, you must also add the read scope for that resource type.

The following scopes are required for `monitoring:read`:

| Scope | Description |
|---|---|
| [`droplet:read`](../../droplet/read) | View Droplets |
| [`regions:read`](../../regions/read) | View data center regions |
| [`sizes:read`](../../sizes/read) | View Droplet plan sizes |
| [`actions:read`](../../actions/read) | View events of shared resources that have occurred in the current team |
| [`image:read`](../../image/read) | View images |

## Associated Scopes

Associated scopes are not required, but they support full functionality of the scope they’re associated with.

For example, to create a Droplet, you need `droplet:create`. To tag a Droplet during creation, you additionally need `tag:create`, so `tag:create` is listed as an associated scope for `droplet:create`.

The following scopes are associated with `monitoring:read`:

| Scope | Description |
|---|---|
| [`database:read`](../../database/read) | View Managed Databases |
| [`app:read`](../../app/read) | View App Platform apps |
| [`kubernetes:read`](../../kubernetes/read) | View Kubernetes clusters but not cluster credentials |