open-telemetry / opentelemetry-collector-contrib

Contrib repository for the OpenTelemetry Collector
https://opentelemetry.io
Apache License 2.0
3.06k stars 2.36k forks source link

k8sattributes it`s not working in EKS 1.26 #22036

Closed AndriySidliarskiy closed 1 year ago

AndriySidliarskiy commented 1 year ago

Component(s)

processor/k8sattributes

What happened?

Description

I have an open telemetry colector configuration with k8sattributes but in the log context, I cannot see anything from metadata included in k8sattributes

Steps to Reproduce

Configure k8sattributes In EKS 1.26 with open telemetry collector helm chart.

Expected Result

   - k8s.pod.name
   - k8s.pod.uid
   - k8s.deployment.name
   - k8s.namespace.name

Actual Result

nothing

Collector version

0.77.0

Environment information

Environment

OS: (e.g., "Ubuntu 20.04") Compiler(if manually compiled): (e.g., "go 14.2")

OpenTelemetry Collector configuration

k8sattributes:
      auth_type: "serviceAccount"
      passthrough: false
      filter:
        node_from_env_var: KUBE_NODE_NAME     
      extract:
        metadata:
          - k8s.pod.name
          - k8s.pod.uid
          - k8s.deployment.name
          - k8s.namespace.name
        labels:
          - tag_name: c2i.pipeline.execution
            key: c2i.pipeline.execution
            from: pod
          - tag_name: c2i.pipeline.project
            key: c2i.pipeline.project
            from: pod
        annotations:
          - tag_name: monitoring # extracts value of annotation from pods with key `annotation-one` and inserts it as a tag with key `a1`
            key: monitoring
            from: pod
    pipelines:
      logs/eks:
        exporters:
          - coralogix
        processors:
          # - batch
          # - resourcedetection/env
          - k8sattributes
        receivers:
          - k8s_events
          - filelog
          - filelog/2

Log output

No response

Additional context

No response

github-actions[bot] commented 1 year ago

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

github-actions[bot] commented 1 year ago

This issue has been closed as inactive because it has been stale for 120 days with no activity.

omri-shilton commented 4 months ago

this issue is still happening to me in EKS