Let kepler pod fail when no access to eBPF #1147
jochen-schuettler
started this conversation in
Ideas
Replies: 1 comment
-
@jochen-schuettler good point. Given that the current version is entirely dependent on eBPF metrics, we should trigger a Kepler failure if eBPF is not functioning correctly. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I had a strange problem that kepler monitored only 0 on a given machine. The log showed that accessing eBPF failed. Kepler 0.7.x solved the issues, likely the "libbpf as standard" helped. But I think I would have found the problem much quicker if the kepler pod would fail into an "ERROR" state in that case, instead of going into normal "running" state.
Beta Was this translation helpful? Give feedback.
All reactions