When the main Kubernetes Cluster API is not available and check_mk can not pull new piggyback data, the Tool " Dynamic host configuration" deletes all hosts from the inventory(and metrics history).
Expected behavior
When Kubernetes API is available and there is no host piggyback data == delete host from inventory >> WORKING
When Kubernetes API is not available == wait to pull new data from API before deleting existing inventory >> NOT WORKING
How DCD behaves, depends on how you configure it. Please see the documentation
section about the Dynamic Configuration Daemon and
check your validity and deletion options. Can it be, that you have “checked” the option to
automatically delete hosts for which no piggyback data is available?
Thank for the replies, the solution is exactly what I need, but I do not have the option " Keep hosts while piggyback source sends no piggyback data at all"
Is it because the checkmk version?
Yes. It looks like the screenshot in the documentation is from 1.6 and not 2.0. The option name has changed in 2.0 but it should work the same way. You can read more about it by activating the “Inline help”.
I looked through all menus and options, and it seems that the feature Keep hosts while piggyback source sends no piggyback data at all" does not exist in checkmk 2.0 ?
You need to “add an element” in the “piggyback creation options” for the connector you’re configuring and there you have the option. This exists in 1.6 and 2.0. Here a screenshot from my 1.6.0p25 instance:
As far as I can see, this is the same in 1.6 or 2.0. As I see on your screenshot the option “Delete vanished hosts / Automatically delete hosts without piggyback data” is unchecked, which is I believe what you want. So at least for me this means, that hosts are not deleted when there is no piggyback data for them: Theoretically this should work.
I unchecked " Automatically delete hosts without piggyback data " because if not I would loose all history metrics as hosts are deleted when check_mk is not able to reach Kubernetes API.
I can confirm you that the behavior " Keep hosts while piggyback source sends no piggyback data at all" does not exist/work in check_mk 2.0
The option “Validity of missing data” didnt work when the Kubernetes API is unreachable and " " Automatically delete hosts without piggyback data " is checked.
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.
