Zabbix Documentation 4.4

3.04.05.0 (current)| In development:5.2 (devel)| Unsupported:1.82.02.22.43.23.44.24.4Guidelines

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
Next revision
Previous revision
manual:acknowledges [2019/04/02 06:04]
127.0.0.1 external edit
manual:acknowledges [2020/04/09 06:31] (current)
martins-v ack message maximum characters before ZBXNEXT-5848
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 the problem list to the problem update 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 a problem event, they can go to Zabbix frontend, navigate from the problem list to the problem update 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 13: Line 13:
 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. 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 ​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 **two** ways to access the problem update screen, which allows to acknowledge a problem. ​+There are **several** ways to access the problem update screen, which allows to acknowledge a problem. ​
  
-The first way, you can click in the //Ack// column showing the acknowledgement status of problems in: +  * You may select problems in //​Monitoring//​ -> //​Problems//​ and then click on //Mass update// below the list 
- +  * You can click in the //Ack// column showing the acknowledgement status of problems in: 
-  ​* //​Monitoring -> Dashboard// (//​Problems//​ and //Problems by severity// widgets) +    * //​Monitoring -> Dashboard// (//​Problems//​ and //Problems by severity// widgets) 
-  * //​Monitoring -> Problems//​ +    * //​Monitoring -> Problems//​ 
-  * //​Monitoring -> Problems -> Event details// +    * //​Monitoring -> Problems -> Event details// 
-  * //​Monitoring -> Screens// (//Host group issues//, //Host issues//, //Problems by severity// elements)+    * //​Monitoring -> Screens// (//Host group issues//, //Host issues//, //Problems by severity// elements)
  
 The //Ack// column contains either a '​Yes'​ or a '​No'​ link, indicating an acknowledged or an unacknowledged problem respectively. Clicking on the links will take you to the problem update screen. ​ The //Ack// column contains either a '​Yes'​ or a '​No'​ link, indicating an acknowledged or an unacknowledged problem respectively. Clicking on the links will take you to the problem update screen. ​
  
-The second way, you can click on an unresolved problem cell in: +  * You can click on an unresolved problem cell in: 
- +    * //​Monitoring -> Dashboard// (//Trigger overview// ​widget
-  ​* //​Monitoring -> Dashboard// (//Data overview// and //Trigger overview// ​widgets+    * //​Monitoring -> Overview//​ 
-  * //​Monitoring -> Overview//​ +    * //​Monitoring -> Screens// (//Trigger overview// ​element)
-  * //​Monitoring -> Screens// (//Data overview// and //Trigger overview// ​elements)+
  
 The popup menu contains an //​Acknowledge//​ option that will take you to the problem update screen. The popup menu contains an //​Acknowledge//​ option that will take you to the problem update screen.
Line 49: Line 48:
  
 ^Parameter^Description^ ^Parameter^Description^
-|//​Message// ​ |Enter text to comment on the problem. ​ |+|//​Message// ​ |Enter text to comment on the problem ​(maximum 256 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 [[:​manual/​web_interface/​frontend_sections/​monitoring/​problems#​viewing_details|event detail]] page.  | |//​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 [[:​manual/​web_interface/​frontend_sections/​monitoring/​problems#​viewing_details|event detail]] page.  |
 |//​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 acknowledgement/​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. ​ | |//​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 acknowledgement/​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 on the severity button to update problem severity. ​ | +|//Change severity// ​ |Mark the checkbox and click on 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 on //​Update//​.\\ If read-write permissions exist for none of the selected triggers, the checkbox is disabled.  | 
-|//​Acknowledge// ​     |Mark the checkbox to acknowledge the problem.\\ This option is disabled for already acknowledged ​problems.  | +|//​Acknowledge// ​     |Mark the checkbox to acknowledge the problem.\\ This option is disabled ​if all selected problems are already acknowledged. If at least one is unacknowledged,​ the option is available and in this case it will be possible to acknowledge only the unacknowledged problem(s).\\ It is not possible to add another acknowledgement ​for an already acknowledged ​ ​problem (it is possible to add another comment though).  | 
-|//Close problem// ​  |Mark the checkbox to manually close the problem.\\ ​Closing ​a problem ​in this way is possible ​if the //Allow manual close// option is checked in [[:​manual/​config/​triggers/​trigger|trigger configuration]]. ​ |+|//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 [[:​manual/​config/​triggers/​trigger|trigger configuration]] ​for at least one of the selected problems. Only those problems will be closed that are allowed to be closed when clicking on //​Update//​.\\ If no problem is manually closeable, the checkbox is disabled.\\ Already closed problems will not be closed repeatedly.  |
  
 === Display === === Display ===