Skip to main content

OTEL-068: K8s environment without resourcedetection processor

Severity: warn (advisory)

Rule Details​

resourcedetection adds resource attributes describing the environment the Collector runs in — cloud provider, region, availability zone, node name, container ID. Without it, telemetry from a Kubernetes receiver lacks the context you need to correlate issues to a specific node or availability zone, which is typically the first question during an incident.

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

Options​

This rule has no options.

Examples​

Avoid
receivers:
  k8s_cluster:
    auth_type: serviceAccount

processors:
  memory_limiter:
    check_interval: 5s
    limit_percentage: 80
  batch:
    timeout: 1s
# no resourcedetection
Prefer
receivers:
  k8s_cluster:
    auth_type: serviceAccount

processors:
  memory_limiter:
    check_interval: 5s
    limit_percentage: 80
  resourcedetection:
    detectors: [env, system, gcp, aws]
    timeout: 2s
  batch:
    timeout: 1s

When Not To Use It​

Collectors running on bare-metal hosts with externally-injected resource attributes (via OTEL_RESOURCE_ATTRIBUTES). Document this so the missing processor is intentional.

  • OTEL-067 — K8s environment without k8sattributes processor

Version​

Available since augur v0.1.0.

Further Reading​

Resources​