Zabbix Documentation 3.4

2.23.03.4In development:4.0Unsupported versions:1.82.02.43.2

User Tools

Site Tools


manual:acknowledges

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
manual:acknowledges [2017/08/29 09:56]
martins-v last 20 issues -> problems widget
manual:acknowledges [2018/05/10 15:21] (current)
martins-v consistent spelling fix: acknowledgement
Line 1: Line 1:
-====== 13. Event acknowledgment ​======+====== 13. Event acknowledgement ​======
  
 === Overview === === Overview ===
Line 5: Line 5:
 Problem events in Zabbix can be acknowledged by users. ​ 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 acknowledgment ​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.+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, if another system user spots the same problem, they immediately see if it has been acknowledged and the comments so far.
Line 11: Line 11:
 This way the workflow of resolving problems with more than one system user can take place in a more coordinated way. This way the workflow of resolving problems with more than one system user can take place in a more coordinated way.
  
-Acknowledgment ​status is also used when defining [[manual:​config:​notifications:​action:​operation|action operations]]. 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.+Acknowledgement ​status is also used when defining [[manual:​config:​notifications:​action:​operation|action operations]]. 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. To acknowledge events, a user must have at least read permission to the corresponding trigger.
  
-=== Acknowledgment ​screen ===+=== Acknowledgement ​screen ===
  
-The acknowledgment ​status of problems is displayed in: +The acknowledgement ​status of problems is displayed in: 
  
   * //​Monitoring -> Dashboard// (//​Problems//​ and //System status// widgets)   * //​Monitoring -> Dashboard// (//​Problems//​ and //System status// widgets)
Line 28: Line 28:
 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. 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 acknowledgment ​screen.+Both '​Yes'​ and '​No'​ are links. Clicking them will take you to the acknowledgement ​screen.
  
 {{manual:​acknowledges:​ack.png?​600|}} {{manual:​acknowledges:​ack.png?​600|}}
Line 36: Line 36:
 Any previous comments for the problem are displayed below the message area. Any previous comments for the problem are displayed below the message area.
  
-Event acknowledgment ​in the frontend can be turned on/off in //​Administration//​ -> //​General//​. When turned off, acknowledgment ​related controls are hidden from view except for the operation condition in action operations. Also, while turning ​acknowledgment ​on/off affects the frontend, it remains available via the API.+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 === === Closing problem manually ===
Line 44: Line 44:
 === Display === === Display ===
  
-Acknowledgment ​information is fully displayed in the event details accessible by clicking the time of event in //​Monitoring//​ -> //​Problems//​.+Acknowledgement ​information is fully displayed in the event details accessible by clicking the time of event in //​Monitoring//​ -> //​Problems//​.
  
-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 [[:​manual/​config/​visualisation/​maps/​map#​creating_a_map|map configuration]] and the [[:​manual/​web_interface/​frontend_sections/​monitoring/​dashboard#​dashboard_filter|dashboard filter]]. It is possible to display all problem count, unacknowledged problem count as separated from the total or unacknowledged problem count only.+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 [[:​manual/​config/​visualisation/​maps/​map#​creating_a_map|map configuration]] and the [[:​manual/​web_interface/​frontend_sections/​monitoring/​dashboard#​dashboard_filter|dashboard filter]]. It is possible to display all problem count, unacknowledged problem count as separated from the total or unacknowledged problem count only.
  
-Acknowledgment ​status is displayed in //​Monitoring -> Triggers//. There, ​acknowledgment ​status is also used with the trigger filtering options. You can filter by unacknowledged triggers or triggers with the last event unacknowledged.+Acknowledgement ​status is displayed in //​Monitoring -> Triggers//. There, ​acknowledgement ​status is also used with the trigger filtering options. You can filter by unacknowledged triggers or triggers with the last event unacknowledged.