Logs in Nebius AI Cloud support the LogQL query language. You can use LogQL in the Nebius CLI, Grafana® and LogCLI. This page covers the supported syntax with examples and limitations specific to Nebius AI Cloud.Documentation Index
Fetch the complete documentation index at: https://docs.nebius.com/llms.txt
Use this file to discover all available pages before exploring further.
Stream selectors
Every LogQL query starts with a stream selector inside curly braces. You must always specify the__bucket__ label (or --bucket when using the Nebius AI Cloud CLI) to select the log bucket:
sp_serial: Compute virtual machines (serial logs)sp_mk8s_control_plane: Managed Kubernetes clusters (control plane logs)sp_mk8s_audit_logs: Managed Kubernetes clusters (audit logs)sp_mlflow: Managed MLflow clusterssp_postgres: Managed PostgreSQL clusterssp_cloudapps: Standalone Applicationssp_k8srelease: applications for Managed Kubernetesdefault: user-ingested logs
| Operator | Description | Example |
|---|---|---|
= | Exact match | {__bucket__="sp_postgres", container="pgbouncer"} |
!= | Negation | {__bucket__="sp_postgres", container!="pgbouncer"} |
=~ | Regex match | {__bucket__="sp_postgres", container=~"pg.*"} |
!~ | Regex negation | {__bucket__="sp_postgres", container!~"pgbouncer|odyssey"} |
Line filters
After the stream selector, chain line filters to search the log message text:| Operator | Description | Example |
|---|---|---|
|= | Line contains text | {...} |= "error" |
!= | Line doesn’t contain text | {...} != "healthcheck" |
|~ | Line matches regex | {...} |~ "status=5\\d+" |
!~ | Line doesn’t match regex | {...} !~ "GET /health" |
Examples
Basic log search
Find deadlocks in PostgreSQL® logs:Filter by log level
Search with regex
Find HTTP 5xx status codes:Find slow requests
Limitations
The LogQL implementation in Nebius AI Cloud has the following limitations:-
You must always include
__bucket__in the stream selector, or use the--bucketparameter in Nebius AI Cloud CLI commands. Queries without it return no entries. -
The
stepvalue (interval between points) must be smaller than therangevalue (the interval over which aggregation is performed). - Alerts on aggregated metrics values are not supported.
-
The entries with non-empty
__error__value are ignored. As a result, filtering by error is not possible. -
The following functions are not supported:
bytes_rate,bytes_over_timefunctionsabsent_over_time(because alerts on aggregated metrics values are not supported)topk,bottomkwithout aggregation by label (because no entries are shown when labels are empty)sort,sort_descaggregationswithoutaggregation clausesvectorfunctionapprox_topkaggregation
The Grafana Labs Marks are trademarks of Grafana Labs, and are used with Grafana Labs’ permission. We are not affiliated with, endorsed or sponsored by Grafana Labs or its affiliates. Postgres, PostgreSQL and the Slonik Logo are trademarks or registered trademarks of the PostgreSQL Community Association of Canada, and used with their permission.