[comment]: # aside:2 [comment]: # ({4d52da4e-61d493ca}) # Problem acknowledgment and suppression Problem events in Zabbix can be acknowledged or suppressed by users. [comment]: # ({/4d52da4e-61d493ca}) [comment]: # ({74637f49-fa7fdaab}) ### Updating problems The problem update popup allows you to: - Comment on the problem. - View comments and actions so far. - Change problem severity. - Suppress/unsuppress problem. - Acknowledge/unacknowledge problem. - Change symptom problem to cause problem. - Manually close problem. ![](../../../assets/en/manual/acknowledges/update_problem.png){width="600"} All mandatory input fields are marked with a red asterisk. |Parameter|Description| |--|--------| |*Problem*|If only one problem is selected, the problem name is displayed.
If several problems are selected, *N problems selected* is displayed.| |*Message*|Enter text to comment on the problem (maximum 2048 characters).| |*History*|Previous activities and comments on the problem are listed, along with the time and user details.
For the meaning of icons used to denote user actions see the [event detail](/manual/web_interface/frontend_sections/monitoring/problems#viewing-details) page.
Note that history is displayed if only one problem is selected for the update.| |*Scope*|Define the scope of such actions as changing severity, acknowledging or manually closing problems:
**Only selected problem** - will affect this event only
**Selected and all other problems of related triggers** - in case of acknowledgment/closing problem, will affect this event and all other problems that are not acknowledged/closed so far. If the scope contains problems already acknowledged or closed, these problems will not be acknowledged/closed repeatedly. On the other hand, the number of message and severity change operations are not limited.| |*Change severity*|Mark the checkbox and click the severity button to update problem severity.
The checkbox for changing severity is available if read-write permissions exist for at least one of the selected problems. Only those problems that are read-writable will be updated when clicking *Update*.
If read-write permissions exist for none of the selected triggers, the checkbox is disabled.| |*Suppress*|Mark the checkbox to suppress the problem:
**Indefinitely** - suppress indefinitely
**Until** - suppress until a given time. Both [absolute and relative](/manual/web_interface/time_period_selector) time formats are supported, for example:
`now+1d` - for one day from now (default)
`now/w` - until the end of the current week
`2022-05-28 12:00:00` - until absolute date/time
Note that a simple period (e. g., `1d`, `1w`) is not supported.
Availability of this option depends on the "Suppress problems" user role settings.
See also: [Problem suppression](/manual/events/acknowledgment/suppression)| |*Unsuppress*|Mark the checkbox to unsuppress the problem. This checkbox is active only if at least one of the selected problems is suppressed.
Availability of this option depends on the "Suppress problems" user role settings.| |*Acknowledge*|Mark the checkbox to acknowledge the problem.
This checkbox is available if there is at least one unacknowledged problem among the selected.
It is not possible to add another acknowledgment for an already acknowledged problem (it is possible to add another comment though).| |*Unacknowledge*|Mark the checkbox to unacknowledge the problem.
This checkbox is available if there is at least one acknowledged problem among the selected.| |*Convert to cause*|Mark the checkbox to convert the symptom problem(s) to cause problem(s).| |*Close problem*|Mark the checkbox to manually close the selected problem(s).
The checkbox for closing a problem is available if the *Allow manual close* option is checked in [trigger configuration](/manual/config/triggers/trigger) for at least one of the selected problems. Only those problems will be closed that are allowed to be closed when clicking *Update*.
If no problem is manually closeable, the checkbox is disabled.
Already closed problems will not be closed repeatedly.| [comment]: # ({/74637f49-fa7fdaab}) [comment]: # ({a9b302ca-79474bd8}) ### Problem acknowledgment If a user gets notified about a problem event, they can go to Zabbix frontend, open the problem update popup window of that problem using one of the ways listed below and acknowledge the problem. When acknowledging, they can enter their comment for it, saying that they are working on it or whatever else they may feel like saying about it. This way, if another system user spots the same problem, they immediately see if it has been acknowledged and the comments so far. This way the workflow of resolving problems with more than one system user can take place in a coordinated way. Acknowledgment status is also used when defining [action operations](/manual/config/notifications/action/operation). You can define, for example, that a notification is sent to a higher level manager only if an event is not acknowledged for some time. To acknowledge events and comment on them, a user must have at least read permissions to the corresponding triggers. To change problem severity or close problem, a user must have read-write permissions to the corresponding triggers. There are **several** ways to access the problem update popup window, which allows acknowledging a problem. - You may select problems in *Monitoring* > *Problems* and then click on *Mass update* below the list - You can click *Update* in the *Update* column of a problem in: - *Dashboards* (*Problems* and *Problems by severity* widgets) - *Monitoring > Problems* - *Monitoring > Problems > Event details* - You can click an unresolved problem cell in: - *Dashboards* (*Trigger overview* widget) The popup menu contains an *Update* option that will take you to the problem update window. [comment]: # ({/a9b302ca-79474bd8}) [comment]: # ({bbf37bd1-36ba3858}) Based on acknowledgment information it is possible to configure how the problem count is displayed in the dashboard or maps. To do that, you have to make selections in the *Problem display* option, available in both [map configuration](/manual/config/visualization/maps/map#creating-a-map) and the *Problems by severity* [dashboard widget](/manual/web_interface/frontend_sections/dashboards#adding-widgets). It is possible to display all problem count, unacknowledged problem count as separated from the total or unacknowledged problem count only. Based on problem update information (acknowledgment, etc.), it is possible to configure update operations - send a message or execute remote commands. [comment]: # ({/bbf37bd1-36ba3858}) [comment]: # ({2aaa288c-0d6af14b}) ### Problem suppression Problem suppression offers a way of temporarily hiding a problem that can be dealt with later. This is useful for cleaning up the problem list in order to give the highest priority to the most urgent issues. For example, sometimes an issue may arise on the weekend that is not urgent enough to be dealt with immediately, so it can be "snoozed" until Monday morning. Problem suppression allows to hide a *single* problem, in contrast to suppression through host maintenance, when all problems of the maintenance host are hidden. Operations for trigger actions will be paused for suppressed problems the same way as it is done with [host maintenance](/manual/events/maintenance). [comment]: # ({/2aaa288c-0d6af14b}) [comment]: # ({18563570-d96cee1e}) A problem can be suppressed through the **[problem update](/manual/events/acknowledgment#updating-problems)** window, where suppression is one of the problem update options along with commenting, changing severity, acknowledging, etc. A problem may also be unsuppressed through the same problem update window. **Display** Once suppressed the problem is marked by a blinking ![](../../../assets/en/manual/web_interface/frontend_sections/monitoring/icon_suppression.png) suppression icon in the *Info* column, before being hidden. If suppression is due to host maintenance, the suppression icon in the *Info* column is shown in orange. If both maintenance and manual suppression apply, manual suppression takes priority in the icon color. The suppression icon is blinking while the suppression task is in the waiting list. Once the task manager has suppressed the problem, the icon will stop blinking. If the suppression icon keeps blinking for a long time, this may indicate a server problem, for example, if the server is down and the task manager cannot complete the task. The same logic applies to unsuppression. In the short period after the task is submitted and the server has not completed it, the unsuppression icon is blinking. A suppressed problem may be both hidden or shown, depending on the problem filter/widget settings. When shown in the problem list, a suppressed problem is marked by the suppression icon and suppression details are shown on mouseover: ![](../../../assets/en/manual/web_interface/suppressed_problem_listed.png) Suppression details are also displayed in a popup when positioning the mouse on the suppression icon in the *Actions* column. [comment]: # ({/18563570-d96cee1e})