How to view metrics in Prometheus

​

Prerequisites

1. Install and configure Nebius AI Cloud CLI.
2. If you don’t have a service account for observability services, create one.
3. Make sure that the service account is in a group that has at least the viewer role within your tenant; for example, the default viewers group. You can check this in the Administration → IAM section of the web console. If the service account is not in the required group, click  → Add to group, and select viewers.
4. Issue a static key for the service account using the following command:
   nebius iam static-key issue \
     --name <name_for_the_key> \
     --account-service-account-id <service_account_ID> \
     --service=OBSERVABILITY
   
   Copy the value of the static key from the token parameter of the response. You will need it on later steps.

​

How to connect Prometheus

1. Download the latest release of Prometheus for your platform.
2. Extract the contents and switch to the folder with Prometheus:
   tar xvfz prometheus-***.tar.gz
   cd prometheus-***
   
3. Create the prometheus.yml configuration file that configures Prometheus to retrieve Monitoring metrics. Use one of the following configurations depending on your Prometheus version:
   Prometheus 3.x

   Prometheus 2.x

   scrape_configs:
     - job_name: 'Export time series from Nebius Monitoring'
       honor_labels: true
       scrape_interval: 15s
       scheme: https
       metrics_path: '/projects/<project_ID>/service-provider/prometheus/federate'
       params:
         match[]:
           - '{__name__=~".+"}'
       bearer_token: '<static_key_for_service_account>'
       static_configs:
         - targets:
           - 'read.monitoring.api.nebius.cloud'
   
   In this file, change the following parameters:
   • bearer_token: enter the static key that you got earlier.
   • metrics_path: specify your project ID in the URL. To get the project ID, go to the web console and expand the top list of projects. Next to the project’s name, click  → Copy project ID. Optionally, add a service in the path in the following format:
     metrics_path: '/projects/<project_ID>/buckets/<service>/prometheus/federate'
     
     The following services are available:
     • compute: metrics related to Compute virtual machines.
     • gpu: GPU-related metrics.
     • nbs: metrics related to Compute volumes.
     • sp_storage: metrics related to Object Storage.
     • msp: metrics related to Managed Service for PostgreSQL® and Managed Service for MLflow.
   • match[]: optionally specify which data Prometheus collects by filtering for labels or metric names. For example, to collect only metrics with the disk prefix, set the following value:
     match[]:
       - '{__name__=~"^disk.*"}'
     
   • scrape_interval: you can change the interval, but the recommended interval is no less than 15 seconds.
4. Start Prometheus:
   ./prometheus --config.file=prometheus.yml
   

​

How to explore and manage metrics

{instance_id=~"computeinstance-.*"}