Skip to main content
Nebius Observability Agent for Kubernetes is a Helm chart developed and maintained by Nebius AI Cloud, specifically designed for Managed Service for Kubernetes® clusters. Nebius Observability Agent for Kubernetes provides:
  • Out-of-the-box metrics collection with minimal configuration
  • Built-in metric enrichment (for example, adds cluster ID and other metadata)
  • High reliability and tight integration with Nebius AI Cloud
  • Unified observability agent that can collect logs, metrics and traces

Installation

Basic installation

  1. Connect to your Managed Service for Kubernetes cluster.
  2. Install the Nebius Observability Agent for Kubernetes:
    To use a specific agent version, change the --version value, for example:
  3. Check the installation:

Installation with custom configuration

To customize the agent configuration, create a values.yaml file and install the agent with custom settings:

Configuration

Basic configuration

You can customize the Nebius Observability Agent for Kubernetes behavior by creating a values.yaml file:

Configuration parameters

Log collection settings

  • 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.

Metrics collection settings

  • config.metrics.enabled: Enable or disable metrics collection. Default: true.
  • config.metrics.collectAgentMetrics: Parameter to collect metrics from the Nebius Observability Agent for Kubernetes itself. Default: false.
  • config.metrics.collectK8sClusterMetrics: Parameter to collect Kubernetes cluster-level metrics. Default: false.
  • config.metrics.excludedNamespaces: List of namespaces to exclude from metrics collection.
  • config.metrics.labelAllowlist: Regular expressions that control which labels from Pod, Service and Node objects are attached to scraped metrics. Each field (podLabels, serviceLabels, nodeLabels) is matched against label names.
    Default: ".+" (all labels are attached).
  • config.metrics.batch.maxSizeBytes: Maximum size, in bytes, of a single metrics export request. Batches exceeding the limit are split before sending. Default: 62914560 (60 MiB).
  • config.metrics.batch.maxSizeMessages: Maximum number of data points in a single metrics export request. Batches exceeding the limit are split before sending. Default: 500000.

Traces collection settings

  • config.traces.enabled: Enable or disable trace collection. Default: true.
When traces are enabled, the agent exposes an OTLP endpoint for receiving traces from your applications:
Where <namespace> is the namespace where the agent is installed (for example, observability).

Full observability configuration

To collect logs, metrics and traces, configure the values.yaml file in the following way:

Logs-only configuration

To collect only logs, configure the values.yaml file in the following way:

Metrics-only configuration

To collect only metrics, configure the values.yaml file in the following way:

Combined logs and metrics configuration

To collect both logs and metrics, configure the values.yaml file in the following way:

Traces-only configuration

To collect only traces, configure the values.yaml file in the following way:

Namespace exclusions

By default, the agent excludes the kube-system namespace to avoid collecting system-level logs and metrics. You can exclude additional namespaces by adding them to the excludedNamespaces list:

Updating the agent

To update the Nebius Observability Agent for Kubernetes to a newer version, use the following command:

Uninstalling the agent

To remove the Nebius Observability Agent for Kubernetes, use the following command:

Troubleshooting

If you encounter issues with the agent:
  1. Check the agent pod status:
  2. View agent logs:
  3. Verify the configuration:

See also