[Yandex Cloud documentation](../../index.md) > [Yandex Compute Cloud](../index.md) > [Step-by-step guides](index.md) > Viewing metrics in Monitoring

# Viewing metrics in Yandex Monitoring

To download metric data, use the [read](../../monitoring/api-ref/MetricsData/read.md) method.

### Getting started {#before-you-begin}

To follow the examples in this section:

1. Make sure you have installed [cURL](https://curl.haxx.se) that is used in the examples.
1. [Get the ID of the folder](../../resource-manager/operations/folder/get-id.md) for which you have the `monitoring.viewer` role or higher.
1. Get an IAM token:
   * [Guide](../../iam/operations/iam-token/create.md) for a Yandex account user.
   * [Guide](../../iam/operations/iam-token/create-for-sa.md) for service accounts.
   * [Guide](../../iam/operations/iam-token/create-for-federation.md) for a federated account.
   * [Guide](../../iam/operations/iam-token/create-for-local.md) for a local account.

## Getting CPU metrics {#cpu}

1. Create a file with the request body, e.g., `body.json`:
    
    For example, the request below gets metric data on the CPU usage for the VM with the `epdpfhoh1r83********` ID from July 24 to July 31 (00:00 UTC).

    **body.json:**
    ```json
    {
        "query": "cpu_usage{service=\"compute\", resource_id=\"epdpfhoh1r83********\"}",
        "fromTime": "2021-07-24T00:00:00Z",
        "toTime": "2021-07-31T00:00:00Z",
        "downsampling": {
            "maxPoints": 10
        }
    }
    ```

    Where:

    * `query`: Query text:
      * `cpu_usage`: CPU usage.
      * `resource_id`: VM ID.
    * `fromTime`: Start of the period.
    * `toTime`: End of the period.

1. Send the request and save the response to a file, e.g., `output.json`:

    ```bash
    export IAM_TOKEN=CggaATEVAgA...
    curl \
      --request POST \
      --header "Content-Type: application/json" \
      --header "Authorization: Bearer ${IAM_TOKEN}" \
      --data '@body.json' \
      'https://monitoring.api.cloud.yandex.net/monitoring/v2/data/read?folderId=b2ghmo15rmnl********' > output.json
    ```

    Response example:

    **output.json:**
    ```json
    {
        "metrics": [
            {
                "type": "DGAUGE",
                "name": "cpu_usage",
                "labels": {
                    "resource_type": "vm",
                    "cluster": "b2ghmo15rmnl********",
                    "project": "b1gbkpesobgv********",
                    "resource_id": "epdpfhoh1r83********",
                    "service": "compute"
                },
                "timeseries": {
                    "timestamps": [
                        1562069440800,
                        1562405369712,
                        1562741298624,
                        1563077227536,
                        1563413156448,
                        1563749085360,
                        1564085014272,
                        1564420943184
                    ],
                    "doubleValues": [
                        53.6475600118669,
                        65.5547751323391,
                        70.7148916473759,
                        49.4514634827568,
                        54.3817816479781,
                        81.9327383032693,
                        99.3035341016667,
                        99.982002860023
                    ]
                }
            }
        ]
    }
    ```

## Getting disk metrics {#disk}

1. Create a file containing your request body, e.g., `body.json`:

    For example, the request below gets metric data on the disk load from August 9 to August 10 (00:00 UTC).

    **body.json:**
    ```json
    {
        "query": "disk.read_bytes{service=\"compute\", disk=\"fhmhpdpidgen********\"}",
        "fromTime": "2025-08-09T00:00:00Z",
        "toTime": "2025-08-10T00:00:00Z",
        "downsampling": {
            "maxPoints": 10
    }
    }
    ```

    Where:

    * `query`: Query text:
      * `disk.read_bytes`: Number of bytes read from the disk.
      * `service="compute"`: Name of the service associated with the metric.
      * `disk="fhmhpdpidgen********"`: ID of a given disk.
    * `fromTime`: Start of the period.
    * `toTime`: End of the period.

1. Send the request and save the response to a file, e.g., `output.json`:

    ```bash
    export IAM_TOKEN=...
    curl \
      --request POST \
      --header "Content-Type: application/json" \
      --header "Authorization: Bearer ${IAM_TOKEN}" \
      --data '@body.json' \
      'https://monitoring.api.cloud.yandex.net/monitoring/v2/data/read?folderId=b1gsm0k26v1l********' > output.json
    ```

    Response example:

    **output.json:**
    ```json
    {
        "metrics": [
            {
                "name": "disk.read_bytes",
                "labels": {
                    "disk": "fhmhpdpidgen********",
                    "instance": "for-backup",
                    "service": "compute"
                },
                "type": "RATE",
                "timeseries": {
                    "timestamps": [
                        1754697600000,
                        1754707200000,
                        1754716800000,
                        1754726400000,
                        1754736000000,
                        1754745600000,
                        1754755200000,
                        1754764800000,
                        1754774400000
                    ],
                    "doubleValues": [
                        457.38666666666666,
                        525.6533333333333,
                        122.45333333333333,
                        442.88,
                        419.4133333333333,
                        360.1066666666667,
                        387.41333333333336,
                        381.8666666666667,
                        561.4933333333333
                    ]
                }
            }
        ]
    }    

You can also view metrics in the [management console](https://console.yandex.cloud). To do this, click ![image](../../_assets/console-icons/dots-9.svg) **All services** on the left-hand panel and select ![image](../../_assets/console-icons/monitoring-icon.svg) **Monitoring** or find it using the search bar on the dashboard.