Set Service Status
can be used to forcibly change the state of a Host or Service Check at a Host
Group, Host or Service Check level. For example, you may wish to test that Notifications are working for a key Service Check. You could either amend the Service Check and wait for it to fail or you could use ‘Set Service Status’ to forcibly change the
service check to ‘CRITICAL’, thus triggering the notifications.
Note: in order to force the Notification to trigger in this example, a number of 'Set Service Status' changes must be submitted within the 'Retry Interval' to order to pass the configured 'Max Check Attempts' limit (by default, 'Max Check Attempts' is three and the Retry Interval is one minute).
Comments can also be
added when a Service Check status is changed, i.e. “Changing to critical to test Notifications”. As the Service Check is changed to CRITICAL in our example, the
‘Retry interval’ will kick-in and the Service Check will be re-checked
automatically (thus likely to return to an OK state within 1 minute).