Skip to main content
Nebius AI Cloud observability services use two agents for different purposes: See the detailed comparison of the two agents below:
FeatureNebius Observability Agent for KubernetesMonitoring agent
PurposeIngests logs from Managed Service for Kubernetes clusters into LoggingCollects system-level metrics (CPU, RAM, GPU, etc.) and journald logs from Compute VMs
Deployed onManaged Service for Kubernetes clustersCompute virtual machines and Managed Service for Kubernetes nodes
Collected dataApplication and infrastructure logsSystem metrics (e.g., GPU, vCPU, memory, OS) and journald logs
InstallationManual (via Helm chart)Automatic (preinstalled on new VMs and Managed Kubernetes nodes)
ComponentsHelm chart with the log collection agentnebius-observability-agent, nebius-observability-agent-updater
Data enrichmentAdds metadata: cluster ID, pod name, container image tag, etc.Adds labels: resource ID, project ID, etc.
Data destinationNebius AI Cloud LoggingNebius AI Cloud Monitoring (web console dashboards)
ManagementVersion controlled via Helm and customizable installationManaged via SSH, supports disabling updates
Use caseCentralized log ingestion for observability and troubleshootingVisual monitoring of infrastructure resource usage