manual:web_interface:frontend_sections:configuration:actions

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:web_interface:frontend_sections:configuration:actions [2017/10/13 11:16]
natalja.cernohajeva
manual:web_interface:frontend_sections:configuration:actions [2018/03/27 14:10]
natalja.cernohajeva Some links added (operations, notification, remote command)
Line 11: Line 11:
 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. 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: ​ An action is displayed to the user without Super-admin rights if the following conditions are fulfilled: ​
-  * The user has read-write access to all elements ​in action conditions ​(host, host group, triggeretc.); +  * The user has read-write access to host groups, hosts, templates and triggers ​in action conditions 
-  * The user is a member of all the user groups notifications are sent to. Otherwise this user will not be able to view this action+  * The user has read-write access to host groupshosts and templates in action operationsrecovery operations and acknowledgement operations 
 +  * The user has read access ​to user groups and users in action ​operations, recovery operations and acknowledgement operations ​
  
  
Line 22: Line 23:
 |//​Name// ​ |Name of the action. Clicking on the action name opens the action [[manual:​config:​notifications:​action#​configuring_an_action|configuration form]]. ​ | |//​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. ​  | |//​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. ​ |+|//[[manual:​config:​notifications:​action:​operation#​configuring_an_operation|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. ​\\ Action operation can both be a [[manual:​config:​notifications:​action:​operation:​message|notification]] or a [[manual:​config:​notifications:​action:​operation:​remote_command|remote command]] depending on the selected type of operation. ​  |
 |//​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. ​ | |//​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. ​ |