I’m not sure, but I think I found the correct way, but it is interpreted wrong by CheckMK:
- I changed the “Normal check interval for host checks” to 44 seconds
- I changed the “Maximum number of check attempts for host” to 25000
By that every 110 seconds (44 seconds x 2,5 intervals) a Host State Change is triggered and as the maximum is 25000 its host state changes from “SOFT (DOWN)” to “HARD (DOWN)” after around one month (25000 seconds x 110 seconds = 31.8 days).
By that the host check attempt counts upwards as expected:
But although the Host state is not “HARD (DOWN)” it is treated as a problem:
I mean why is a “SOFT (DOWN)” host a problem which needs action by the user? Sounds like a bug to me.