Run a PromQL instant query (project-scoped).

POST

/v1/projects/{projectId}/observability/metrics/actions/query-instant

Code sample: Shell / cURL

curl --request POST \
  --url https://stratum.example.com/v1/projects/example/observability/metrics/actions/query-instant \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{ "query": "example", "time": "2026-04-15T12:00:00Z", "category": "platform" }'

• A Stratum cluster endpoint.

Cedar action observability:GetMetricStatistics. The Stratum API prefix-injects project_id="<pid>" into the PromQL selector before forwarding to VictoriaMetrics; the customer query MUST NOT reference project_id (rejected with 400 INVALID_INPUT). Complex aggregations are supported as long as the selector carries the injected label.

Authorizations

• bearerAuth

Parameters

Path Parameters

projectId

required

string

/^p-[a-z0-9-]+$/

Request Body^required

Media typeapplication/json

object

query

required

PromQL expression.

string

time

Evaluation timestamp (defaults to now).

string format: date-time

category

. Optional narrowing label. Forwarded to VictoriaMetrics as an extra_filters[] entry so it composes AST-correctly with the customer’s PromQL (same mechanism that injects project_id). The operator surface defaults to platform; the tenant surface defaults to workload — the UI sets this per route.

string

Allowed values: platform workload

Responses

200

Vector samples.

Media typeapplication/json

The complete result of the submitted instant query.

Not a paginated collection, and not a bounded catalog either: its size is set by the query — one sample per series the selector matches — rather than by how many rows exist. There is no nextPageToken, because the way to get a smaller result is to ask a narrower question.

object

items

required

Array<object>

object

metric

required

object

key

additional properties

string

timestamp

required

string format: date-time

value

required

number format: double

Example ^generated

{
  "items": [
    {
      "metric": {
        "additionalProperty": "example"
      },
      "timestamp": "2026-04-15T12:00:00Z",
      "value": 1
    }
  ]
}

400

Bad request.

Media typeapplication/problem+json

object

type

required

string format: uri

title

required

string

status

required

integer

>= 400 <= 599

detail

string

instance

string format: uri-reference

requestId

required

string

code

required

string

issues

The findings of a rejected IAM policy document (custom and resource policies).

Array<object>

One finding of a rejected IAM policy document. A rejection lists every finding, so the author fixes the document in one round trip.

object

code

required

The finding, e.g. INVALID_DOCUMENT, UNKNOWN_ACTION, ACTION_NOT_APPLICABLE.

string

statement

required

Index of the statement at fault; -1 for the document as a whole.

integer

>= -1

detail

required

string

action

The offending action, where one is at fault (ACTION_NOT_APPLICABLE).

string

errors

Field errors, for codes that carry them: each problem at its field (see FieldError). Documented on the responses that set it, e.g. approveNodeJoin’s INVALID_INPUT and JOIN_APPROVAL_REFUSED. Absent otherwise.

Array<object>

One field’s problem, the stage-2 installer API’s shape. field is the field’s path, message what is wrong with it.

object

field

required

The field’s path, e.g. links[0].interface, disks[1].confirm, mgmt.address or role; empty for the whole request.

string

message

required

string

details

Structured facts about the refusal, for codes that carry them. The shape is fixed per code and documented on the response that answers it, e.g. IMAGE_POOL_MISMATCH (see ImagePoolMismatchDetails) and IMAGE_IN_USE. Absent for codes that carry none.

object

key

additional properties

any

Example

{
  "issues": [
    {
      "code": "ACTION_NOT_APPLICABLE",
      "action": "compute:CreateVpc"
    }
  ]
}

503

Upstream temporarily unavailable (driver / scheduler / dependency).

Media typeapplication/problem+json

object

type

required

string format: uri

title

required

string

status

required

integer

>= 400 <= 599

detail

string

instance

string format: uri-reference

requestId

required

string

code

required

string

issues

The findings of a rejected IAM policy document (custom and resource policies).

Array<object>

One finding of a rejected IAM policy document. A rejection lists every finding, so the author fixes the document in one round trip.

object

code

required

The finding, e.g. INVALID_DOCUMENT, UNKNOWN_ACTION, ACTION_NOT_APPLICABLE.

string

statement

required

Index of the statement at fault; -1 for the document as a whole.

integer

>= -1

detail

required

string

action

The offending action, where one is at fault (ACTION_NOT_APPLICABLE).

string

errors

Field errors, for codes that carry them: each problem at its field (see FieldError). Documented on the responses that set it, e.g. approveNodeJoin’s INVALID_INPUT and JOIN_APPROVAL_REFUSED. Absent otherwise.

Array<object>

One field’s problem, the stage-2 installer API’s shape. field is the field’s path, message what is wrong with it.

object

field

required

The field’s path, e.g. links[0].interface, disks[1].confirm, mgmt.address or role; empty for the whole request.

string

message

required

string

details

Structured facts about the refusal, for codes that carry them. The shape is fixed per code and documented on the response that answers it, e.g. IMAGE_POOL_MISMATCH (see ImagePoolMismatchDetails) and IMAGE_IN_USE. Absent for codes that carry none.

object

key

additional properties

any

Example

{
  "issues": [
    {
      "code": "ACTION_NOT_APPLICABLE",
      "action": "compute:CreateVpc"
    }
  ]
}