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/08/15 11:36]
martins-v more precise wording
manual:acknowledges [2020/05/07 08:35] (current)
martins-v problem name parameter added (ZBX-17584)
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, ​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, 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.+This way the workflow of resolving problems with more than one system user can take place in a coordinated way.
  
 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.
Line 15: Line 15:
 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. 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 ​screen, which allows to acknowledge a problem. ​+There are **several** ways to access the problem update ​popup window, which allows to acknowledge a problem. ​
  
   * You may select problems in //​Monitoring//​ -> //​Problems//​ and then click on //Mass update// below the list   * You may select problems in //​Monitoring//​ -> //​Problems//​ and then click on //Mass update// below the list
Line 24: Line 24:
     * //​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 ​popup window
  
   * You can click on an unresolved problem cell in:   * You can click on an unresolved problem cell in:
-    * //​Monitoring -> Dashboard// (//Data overview// and //Trigger overview// ​widgets)+    * //​Monitoring -> Dashboard// (//Trigger overview// ​widget)
     * //​Monitoring -> Overview//     * //​Monitoring -> Overview//
-    * //​Monitoring -> Screens// (//Data overview// and //Trigger overview// ​elements)+    * //​Monitoring -> Screens// (//Trigger overview// ​element)
  
-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 ​window.
  
 === Updating problems === === Updating problems ===
  
-The problem update ​screen ​allows to:+The problem update ​popup allows to:
  
   * comment on the problem ​   * comment on the problem ​
   * view comments and actions so far   * view comments and actions so far
   * change problem severity   * change problem severity
-  * acknowledge problem+  * acknowledge/​unacknowledge ​problem
   * manually close problem   * manually close problem
  
-{{manual:​acknowledges:​update_problem1.png|}}+{{manual:​acknowledges:​update_problem.png?600|}}
  
 All mandatory input fields are marked with a red asterisk. ​ All mandatory input fields are marked with a red asterisk. ​
  
 ^Parameter^Description^ ^Parameter^Description^
-|//​Message// ​ |Enter text to comment on the problem. ​ | +|//​Problem// ​ |If only one problem is selected, the problem name is displayed.\\ If several problems are selected, //N problems selected// is displayed. ​ | 
-|//​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.  |+|//​Message// ​ |Enter text to comment on the problem ​(maximum 2048 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.\\ Note that history is displayed if only one problem is selected for the update.  |
 |//​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.\\ ​Read-write permissions ​to all corresponding triggers ​are required.  | +|//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 ​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). ​ | +|//​Acknowledge// ​     |Mark the checkbox to acknowledge the problem.\\ This checkbox ​is available ​if there is at least one unacknowledged ​problem among the selected.\\ 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 selected problem(s).\\ Read-write permissions to all corresponding triggers are required.\\ 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. ​ |+|//​Unacknowledge// ​ |Mark the checkbox to unacknowledge the problem.\\ This checkbox is available if there is at least one acknowledged problem among the selected.  | 
 +|//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 ===