You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Metrics scraped with prometheus.operator.podmonitors or prometheus.operator.servicemonitors are missing OpenTelemetry resource attributes about the Pod when using otelcol.receiver.prometheus.
According to the mapping defined in the otelcol.receiver.prometheus the following OpenTelemetry resource attributes should be set (see source code):
k8s.pod.name
k8s.pod.uid
k8s.container.name
k8s.namespace.name
The mapping is done via the Prometheus internal meta labels __meta_kubernetes_ provided via discovered target labels (see here).
By intention, the according Alloy Prometheus Appender implementation Fanout always set an empty Target (see here). Therefore, the mentioned meta labels are not available.
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?
Metrics scraped with
prometheus.operator.podmonitors
orprometheus.operator.servicemonitors
are missing OpenTelemetry resource attributes about the Pod when usingotelcol.receiver.prometheus
.Steps to reproduce
System information
Linux 6.5.0-28 x86_64
Software version
Grafana Alloy 1.0.0
Configuration
Grafana Alloy configuration:
Example ServiceMonitor for Istiod:
Logs
Example OTEL Logging output:
The text was updated successfully, but these errors were encountered: