Open lieberlois opened 7 months ago
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!
any news?
@algo7 I think it was just a matter of bad docs. Apparently the k8sattributes modules only really work with the push based approach via OTLP, at least from what i figured.
What's wrong?
Im trying to setup the otelcol.processor.k8sattributes with Grafana Loki. Unfortunately, the k8sattributes processor seems to not be capable of extracting the k8s metadata from the loki.source.kubernetes module. The module outputs no new labels. My assumption is that it doesnt work because loki.source.kubernetes does not expose k8s.pod.ip, which the k8sattributes processor uses for pod matching
This is my config:
The pipeline thus looks like this:
The debug component however only writes this to the console (there is a ubuntu container in the default namespace that writes hello world to stdout):
Steps to reproduce
kubectl run -n default ubuntu --image=ubuntu:latest -- sh -c 'while true; do echo "hello world"; sleep 1; done'
kubectl logs alloy-infra-0 -f
System information
Linux, Azure AKS
Software version
Grafana Alloy v1.0.0
Configuration
Logs