Is there a way to prevent the overlay filesystem from being discovered when monitoring the Kubernetes nodes with CheckMK agents?
Firstly, it is unnecessary and secondly, it is very annoying when countless UNKNOWN messages appear in CheckMK with every deployment change.
Currently I have more or less “solved” it by setting the periodic service discovery for the Kubernetes nodes to every two minutes so that the messages are only visible for a relatively short time.
The service discovery rule filesystem discovery is unfortunately very limited.
I would solve this with a rule of type “Disabled services” and “Filesystem overlay” or “Filesystem overlay /run/” as a service matching pattern.
1 Like
Thank you, that solves the problem. But in my opinion it is not a nice solution.
I think it would be necessary to extend the rule “Filesystem discovery” so that a pattern can be defined there.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed. Contact an admin if you think this should be re-opened.