How to ingest metrics from a Vector instance

​

Prerequisites

1. Install and configure the 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 editor role within your tenant; for example, the default editors 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 editors. Only users with the admin role can add a service account to a group.
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 later in the configuration steps.

​

How to configure a sink

1. Add the following remote_write section to the Vector configuration file:
   # Gather metrics from sources (for example, Vector's metrics from Vector itself)
   sources:
     vector_metrics:
       type: "internal_metrics"
      scrape_interval_secs: 15
   
   # Optional transformations
   
   # Send metrics to Observability via remote_write
   sinks:
     prometheus_remote_write:
       type: "prometheus_remote_write"
       inputs:
         - "vector_metrics"
       endpoint: "https://write.monitoring.<region_ID>.nebius.cloud/projects/<project_ID>/prometheus/api/v1/write"
       auth:
         strategy: "bearer"
         token: "<token_value>"
       healthcheck:
         enabled: false
   
   In this configuration, specify the following values:
   • Region ID from the region list.
   • Project ID.
   • Token value of the static key that you got earlier.
2. Restart or reload your Vector instance.