[comment]: # ({93d6f917-ad0fbcd3})
# 2 Manual closing of problems

[comment]: # ({/93d6f917-ad0fbcd3})

[comment]: # ({12a79efb-0eef1445})
#### Overview

While generally problem events are resolved automatically when trigger
status goes from 'Problem' to 'OK', there may be cases when it is
difficult to determine if a problem has been resolved by means of a
trigger expression. In such cases, the problem needs to be resolved
manually.

For example, *syslog* may report that some kernel parameters need to be
tuned for optimal performance. In this case the issue is reported to
Linux administrators, they fix it and then close the problem manually.

Problems can be closed manually only for triggers with the *Allow manual
close* option enabled.

When a problem is "manually closed", Zabbix generates a new internal
task for Zabbix server. Then the *task manager* process executes this
task and generates an OK event, therefore closing problem event.

A manually closed problem does not mean that the underlying trigger will
never go into a 'Problem' state again. When new data arrive for any item
included in the trigger expression, the whole expression is re-evaluated
and may result in a problem again.

[comment]: # ({/12a79efb-0eef1445})

[comment]: # ({ece5ae52-ece5ae52})
#### Configuration

Two steps are required to close a problem manually.

[comment]: # ({/ece5ae52-ece5ae52})

[comment]: # ({a7804eac-8e977ac6})
##### Trigger configuration

In trigger configuration, enable the *Allow manual close* option.

![](../../../../assets/en/manual/config/manual_close_conf.png)

[comment]: # ({/a7804eac-8e977ac6})

[comment]: # ({00fc8cb0-229474e2})
##### Event acknowledgement

If a problem arises for a trigger with the *Manual close* flag, you can
go to the acknowledgement screen of that trigger and close the problem
manually.

To close the problem, check the *Close problem* option in
acknowledgement form and click on *Acknowledge*.

![](../../../../assets/en/manual/config/ack_close_problem.png)

All mandatory input fields are marked with a red asterisk.

The request is processed by Zabbix server. Normally it will take a few
seconds to close the problem. During that process *CLOSING* is displayed
in *Monitoring* → *Problems* as the status of the problem.

[comment]: # ({/00fc8cb0-229474e2})

[comment]: # ({b779710d-a2933506})
#### Verification

It can be verified that a problem has been closed manually:

-   in event details, available through *Monitoring* → *Problems*;
-   by using the {EVENT.ACK.HISTORY} macro in notification messages that
    will provide this information.

[comment]: # ({/b779710d-a2933506})