Closed rirouxe closed 7 years ago
Thanks, i fixed demo.thruk.org :-)
Well, Thruk just submits the command and it looks like that worked. Everything else is up to the core (Nagios/Naemon/Icinga). You could check if there is a command for this service defined because its not required for passive checks.
If icinga receives the command but doesn't do the right thing, its an icinga issue.
ok thanks
Hello
on thruk 2.14-2 and red hat 7.3
the command re-schedule next check not working
i submit a critical alert and when i re-schedule, my alert stay critical
I have to wait for the next planning so that it goes back ok
icinga log's :
PS : demo thruk is broken