​
Overview

By adding Kubernetes-specific attributes to telemetry signals, you can gain better visibility into workloads running in the cluster.

Helps in correlating traces, logs and metrics with specific Kubernetes resources, such as pods, deployments, nodes and clusters.

Adding resource attributes based on custom kubernetes annotations/labels can enrich the data with user defined aggregations and metadata corresponding to the originating pod that produced the telemetry.

​
Configuration Options

​
Basic Example

The following example demonstrates how to collect Kubernetes attributes, including labels and annotations, and attach them to telemetry signals.

k8s-attributes.yaml
apiVersion: actions.odigos.io/v1alpha1
kind: K8sAttributes
metadata:
  name: collect-k8s-attributes
  namespace: odigos-system
spec:
  actionName: "Collect Kubernetes Attributes"
  collectContainerAttributes: true
  collectWorkloadUID: true
  collectClusterUID: true
  labelsAttributes:
    - labelKey: "app.kubernetes.io/name"
      attributeKey: "app.kubernetes.name"
  annotationsAttributes:
    - annotationKey: "kubectl.kubernetes.io/restartedAt"
      attributeKey: "kubectl.kubernetes.restartedAt"
  signals:
    - TRACES
    - METRICS
    - LOGS

kubectl apply -f k8s-attributes.yaml
PII MaskingError Sampler