Acknowledgements

Acknowledgements are a way of disabling notifications for a host/service. It allows the user to put a comment to show the current situation for that object. This is a way of handling “unplanned outages”.

If requested, an acknowledgement notification will be sent to all the contacts that get failure notifications.

Acknowledgements also put a host/service into a handled state, so that they can be displayed in different status views.

When a host or service moves from a failure state back to UP or OK, then the acknowledgement is cleared. If you need to disable notifications for a certain period of time, we recommend using scheduled downtime instead, as this fixes a time period for disabling notifications. Downtimes are also considered “handled”.

In Opsview 3, the comment will be removed when the object recovers to an OK state.

In a distributed environment, acknowledgements are sent to all slaves, but only the active slave (or cluster node) will process the acknowledgement. This means that the acknowledgement will be set at the slave as well as the master.

Note: if a host moves to a different slave, the acknowledgement does not move with it, so you may get an alert. This is a known limitation.

This screen allows you to acknowledge lots of hosts or services all at once.

Only hosts/services that are in an unhandled state will be listed here. If a host is failed, then all the failed services on it are grouped together. The list is also filtered according to the services the current user is allowed to change.

You have to add a comment for the acknowledgement.

You can optionally choose to send out an acknowledgement notification. This will go to all contacts that would normally receive notifications for this host/service.

The Toggle All Checkboxes is a helper to enable/disable all subsequent checkboxes.

When you submit, the changes are submitted to Nagios, but may take a few moments to take effect.