# 13. Event acknowledgement

#### Overview

Problem events in Zabbix can be acknowledged by users.

If a user gets notified about of a problem event, they can go to Zabbix
frontend, navigate from events to the acknowledgement screen 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 more coordinated way.

Acknowledgement status is also used when defining [action
operations](/fr/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, a user must have at least read permission to the
corresponding trigger.

#### Acknowledgement screen

The acknowledgement status of problems is displayed in:

-   *Monitoring → Dashboard* (*Problems* and *Problems by severity*
    widgets)
-   *Monitoring → Problems*
-   *Monitoring → Problems → Event details*
-   *Monitoring → Overview* (with triggers selected)
-   *Monitoring → Screens* (with *Host group issues*, *Host issues*,
    *Problems by severity* and *Triggers overview* elements)

The *Ack* column contains either a 'Yes' or a 'No', indicating an
acknowledged or an unacknowledged problem respectively. A 'Yes' may also
have a number with it, indicating the number of comments for the problem
so far.

Both 'Yes' and 'No' are links. Clicking them will take you to the
acknowledgement screen.

![](../../assets/en/manual/acknowledges/ack.png){width="600"}

All mandatory input fields are marked with a red asterisk.

To acknowledge a problem, enter your comment and click on *Acknowledge*.
You may choose to acknowledge the selected event only or the selected
event and all other unacknowledged problems of the trigger(s).

Any previous comments for the problem are displayed below the message
area.

Event acknowledgement in the frontend can be turned on/off in
*Administration* → *General*. When turned off, acknowledgement related
controls are hidden from view except for the operation condition in
action operations. Also, while turning acknowledgement on/off affects
the frontend, it remains available via the API.

#### Closing problem manually

You can [manually close](/manual/config/events/manual_close) a problem
through the acknowledgement screen by checking the *Close problem*
option. Closing a problem in this way is possible if the *Allow manual
close* option is checked in [trigger
configuration](/manual/config/triggers/trigger).

#### Display

Acknowledgement information is fully displayed in the event details
accessible by clicking the time of event in *Monitoring* → *Problems*.

Based on acknowledgement 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 [dashboard
filter](/manual/web_interface/frontend_sections/monitoring/dashboard#dashboard_filter).
It is possible to display all problem count, unacknowledged problem
count as separated from the total or unacknowledged problem count only.