Beyla looses K8s metadata after ~20m

[mariomac]

Observed at least in process and RED metrics. Beyla eventually stops reporting the kubernetes metadata of pods. None of the instrumented pods were restarted at that time.

Observed with:

• Beyla 1.8
• Prometheus exporter
• Running Kind on Mac+Colima

[grcevski]

Actually I noticed this as well, but I've only been able to reproduce it once. I had my laptop wake up from sleep and I had a running cluster with Beyla on, when I restarted the load generator to drive some traffic, all services came in with their executable names, like the k8s DB was empty. My guess is that somehow we lost a reference to the DB, it might've lost the internal maps or something like it.

[marevers]

Seen this exact behavior as well, since 1.8.0, the service_name label seems to revert to the executable name, in my case it would after some time display java everywhere.

[mariomac]

@marevers Beyla 1.8.3 https://github.com/grafana/beyla/releases/tag/v1.8.3 fixes it