Skip to main content

OTEL-067: K8s environment without k8sattributes processor

Severity: warn (advisory)

Rule Details​

Receivers like kubeletstats, k8s_cluster, k8s_events, and k8sobjects pull telemetry from Kubernetes APIs — but on their own they tag each item with the source component, not the pod, namespace, deployment, or node the metric actually describes. The k8sattributes processor enriches each item with that metadata so you can actually slice dashboards by workload.

This rule fires when a Kubernetes receiver is configured but no k8sattributes processor exists.

Options​

This rule has no options.

Examples​

Avoid
receivers:
  kubeletstats:
    collection_interval: 30s
    auth_type: serviceAccount

processors:
  memory_limiter:
    check_interval: 5s
    limit_percentage: 80
  batch:
    timeout: 1s
# no k8sattributes
Prefer
receivers:
  kubeletstats:
    collection_interval: 30s
    auth_type: serviceAccount

processors:
  memory_limiter:
    check_interval: 5s
    limit_percentage: 80
  k8sattributes:
    auth_type: serviceAccount
    passthrough: false
  batch:
    timeout: 1s

When Not To Use It​

A pipeline that feeds a backend which already enriches with Kubernetes metadata on ingest. In that case document the assumption explicitly.

  • OTEL-068 — K8s environment without resourcedetection processor

Version​

Available since augur v0.1.0.

Further Reading​

Resources​