|*Suppress*|Mark the checkbox to suppress the problem:<br>**Indefinitely** - suppress indefinitely<br>**Until** - suppress until a given time. Both [absolute and relative](/manual/web_interface/time_period_selector) time formats are supported, for example:<br>`now+1d` - for one day from now (default)<br>`now/w` - until the end of the current week<br>`2022-05-28 12:00:00` - until absolute date/time<br>Note that a simple period (e. g., `1d`, `1w`) is not supported.<br>Availability of this option depends on the "Suppress problems" user role settings.<br>See also: [Problem suppression](/manual/acknowledgment/suppression)|
<?xml version='1.0' encoding='UTF-8'?>
<xliff xmlns="urn:oasis:names:tc:xliff:document:1.2" version="1.2">
<file source-language="en" target-language="zh-CN" datatype="plaintext" original="manual/acknowledgment.md">
<trans-unit id="61d493ca" xml:space="preserve">
<source># 13 Problem acknowledgment</source>
<target># 13. 问题确认</target>
<trans-unit id="79474bd8" xml:space="preserve">
Problem events in Zabbix can be acknowledged by users.
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 on *Update* in the *Update* column of a problem in:
- *Dashboards* (*Problems* and *Problems by severity*
- *Monitoring → Problems*
- *Monitoring → Problems → Event details*
- You can click on 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.</source>
如果用户收到有关问题事件的通知,他们可以进入Zabbix前端,通过以下列出的任一方式打开该问题的问题更新弹出窗口,并对问题进行确认。在确认时,他们可以提交他们关于此问题的处理意见和当时的想法,比如可以表示正在处理该问题或者关于这个问题提供一些其他相关信息。
通过这种方式,如果另一个管理员发现了相同的问题,他们可以立即看到该问题是否已被确认以及最新的相关描述。
这种方式可以使多个设备管理用户协调解决问题的工作流程得以实现。
确认状态在定义 [动作操作](/manual/config/notifications/action/operation)时也会用到。例如,您可以定义,只有在一段时间内未确认事件时,通知才会发送给更高级别的管理者。
要确认事件并对其进行评论,用户必须至少具有对应触发器的读取权限。要更改问题的严重性或关闭问题,则需要用户具有对应触发器的读写权限。