Skip to main content
Nebius Observability Agent for Kubernetes collects workload logs (Pod logs) from your Managed Service for Kubernetes cluster and forwards them to Observability Logs. To install the Nebius Observability Agent for Kubernetes in your Managed Service for Kubernetes cluster, follow the guide in Nebius Observability Agent for Kubernetes. By default, the agent automatically collects logs from all workloads in your cluster. After installation, logs will appear in the default bucket in Observability Logs.
Connect Grafana® to view ingested logs within it.

​
Log collection configuration

You can customize log collection by creating a values.yaml file and updating your Nebius Observability Agent for Kubernetes installation:

​
Basic log configuration

​
Configuration parameters

  • config.logs.enabled: Enable or disable log collection. Default: true.
  • config.logs.collectAgentLogs: Parameter to collect logs from the Nebius Observability Agent for Kubernetes itself. Default: false.
  • config.logs.excludedNamespaces: List of namespaces to exclude from log collection.

​
Excluding namespaces

To avoid collecting logs from infrastructure or monitoring namespaces, exclude specific namespaces from the log collection:

​
Data enrichment

The Nebius Observability Agent for Kubernetes enriches logs with the following metadata:
  • k8s_cluster_id: Cluster ID
  • k8s_node_group_id: Node group ID
  • app.kubernetes.io/name: Application name label
  • k8s.namespace.name: Namespace name
  • k8s.deployment.name: Deployment name (if applicable)
  • k8s.statefulset.name: StatefulSet name (if applicable)
  • k8s.daemonset.name: DaemonSet name (if applicable)
  • k8s.cronjob.name: CronJob name (if applicable)
  • k8s.job.name: Job name (if applicable)
  • k8s.node.name: Node name
  • k8s.pod.name: Pod name
  • k8s.pod.start_time: Pod start time
  • container.image.tag: Container image tag
  • k8s.container.restart_count: Number of the container restarts in the Pod
  • k8s_pod_uid: Pod unique identifier

​
Troubleshooting

If you encounter issues with log or metric collection, do the following:
  1. Verify the agent is running:
  2. Check agent logs for errors:
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.