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

Link to this comparison view

Both sides previous revision Previous revision
Previous revision
manual:web_interface:frontend_sections:configuration:actions [2017/10/30 14:03]
manual:web_interface:frontend_sections:configuration:actions [2017/10/30 14:12] (current)
Line 1: Line 1:
 +==== 5 Actions ====
 +=== Overview ===
 +In the //​Configuration -> Actions// section users can configure and maintain actions.
 +A listing of existing actions with their details is displayed. The actions displayed are actions assigned to the selected event source (triggers, discovery, auto-registration).
 +To view actions assigned to a different event source, change the source from the dropdown to the right in the //Actions// bar.
 +For users without Super-admin rights actions are displayed according to permission settings. ​ That means in some cases a user without Super-admin rights isn’t able to view the complete ​ action list because of certain permission restrictions.
 +An action is displayed to the user without Super-admin rights if the following conditions are fulfilled: ​
 +  * The user has read-write access to host groups, hosts, templates and triggers in action conditions
 +  * The user has read-write access to host groups, hosts and templates in action operations
 +  * The user has read access to user groups and users in action operations  ​
 +Displayed data:
 +|//​Name// ​ |Name of the action. Clicking on the action name opens the action [[manual:​config:​notifications:​action#​configuring_an_action|configuration form]]. ​ |
 +|//​Conditions// ​ |Action conditions are displayed. ​  |
 +|//​Operations// ​ |Action operations are displayed.\\ Since Zabbix 2.2, the operation list also displays the media type (e-mail, SMS, Jabber, etc) used for notification as well as the name and surname (in parentheses after the alias) of a notification recipient. ​ |
 +|//​Status// ​ |Action status is displayed - //Enabled// or //​Disabled//​.\\ By clicking on the status you can change it.\\ See the [[:​manual/​config/​notifications/​action/​escalations|Escalations]] section for more details as to what happens if an action is disabled during an escalation in progress. ​ |
 +To configure a new action, click on the //Create action// button in the top right-hand corner.
 +== Mass editing options ==
 +Buttons below the list offer some mass-editing options:
 +  * //Enable// - change the action status to //Enabled//
 +  * //Disable// - change the action status to //​Disabled//​
 +  * //Delete// - delete the actions
 +To use these options, mark the checkboxes before the respective actions, then click on the required button.