Open jseiser opened 4 months ago
Note in the above logs, all those attributes are grafana agent, even though the trace really came a pod called console
in a namespace of qa1-dev
Since all traces have the grafana agent attributes, it makes searching for a specific environments traces near impossible.
If i remove this, i get no attributes
pod_association {
source {
from = "connection"
}
}
This feels similar to this issue: https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/29630
But there doesnt seem to be a solution
Wanted to note, if we actually configure all of the ENV vars for OTLP on the pod, things start to work, but it actuallys/removes any linking between the pods and linkerd.
Have yet to find a way to run grafana agent in eks, that can actually consolidate your traces.
This issue has not had any activity in the past 30 days, so the needs-attention
label has been added to it.
If the opened issue is a bug, check to see if a newer release fixed your issue. If it is no longer relevant, please feel free to close this issue.
The needs-attention
label signals to maintainers that something has fallen through the cracks. No action is needed by you; your issue will be kept open and you do not have to respond to this comment. The label will be removed the next time this job runs if there is new activity.
Thank you for your contributions!
What's wrong?
When running grafana agent in EKS, the resource attributes assigned to every trace are the attributes of the grafana agent pod which processed the trace, not the attributes for the pod that generated the trace.
Steps to reproduce
System information
EKS 1.28
Software version
v0.40.4
Configuration
Logs