Zabbix Documentation 3.4

3.04.04.45.0 (current)| In development:5.2 (devel)| Unsupported:1.82.02.22.43.23.44.2Guidelines

User Tools

Site Tools


manual:config:visualisation:maps:map

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
Last revision Both sides next revision
manual:config:visualisation:maps:map [2017/10/06 13:55]
natalja.cernohajeva adding a link to Host group element section
manual:config:visualisation:maps:map [2018/02/13 14:50]
natalja.cernohajeva Removed "Access based on permissions" section, information is not clear for the users and permissions also covered in "Public and private" maps section
Line 19: Line 19:
 All users in Zabbix (including non-admin users) can create network maps. Maps have an owner - the user who created them. Maps can be made public or private. ​ All users in Zabbix (including non-admin users) can create network maps. Maps have an owner - the user who created them. Maps can be made public or private. ​
  
-  * //Public// maps are visible to all users, although to see it the user must have read access to at least one map element.+  * //Public// maps are visible to all users, although to see it the user must have read access to at least one map element. ​Public maps can be edited in case a user/ user group has read-write permissions for this map and at least read permissions to all elements of the corresponding map including triggers in the links.  ​
  
-  * //Private// maps are visible only to their owner and the users/user groups the map is [[:​manual/​config/​visualisation/​maps/​map|shared]] with by the owner. Regular (non-Super admin) users can only share with the groups and users they are member of. Admin level users can see private maps regardless of being the owner or belonging to the shared user list.  +  * //Private// maps are visible only to their owner and the users/user groups the map is [[:​manual/​config/​visualisation/​maps/​map|shared]] with by the owner. Regular (non-Super admin) users can only share with the groups and users they are member of. Admin level users can see private maps regardless of being the owner or belonging to the shared user list. Private ​maps can be edited by the owner of the map and in case a user/ user group has read-write permissions for this map and at least read permissions to all elements ​of the corresponding map including ​triggers ​in the links.
- +
-=== Access based on permissions === +
- +
-Access to maps and map elements is also limited based on permissions that the type of user has. +
- +
-^Map/element ​ ^Super admin  ^Admin, regular ​user  ^ +
-|Map         ​|Accessible always ​ |Accessible if possessing ​read access to at least one map element. ​ | +
-|Host        |:::|Access is based on permissions to the host (as part of host group). ​ | +
-|Host group  |:::|Access is based on permissions to the host group. ​ | +
-|Trigger ​    ​|:::​|Access is based on permissions to the host (as part of host group) of the trigger. If trigger element consists of multiple ​triggers, the element is accessible if possessing read access to at least one of the trigger | +
-|Image ​      ​|:::​|Accessible always ​ | +
-|Link        |:::​|Accessible always ​ |+
  
 Map elements that the user does not have read permission to are displayed with a greyed out icon and all textual information on the element is hidden. However, trigger label is visible even if the user has no permission to the trigger. Map elements that the user does not have read permission to are displayed with a greyed out icon and all textual information on the element is hidden. However, trigger label is visible even if the user has no permission to the trigger.
Line 102: Line 90:
 |//​Host// ​ |Enter the host, if the element type is '​Host'​. This field is auto-complete so starting to type the name of a host will offer a dropdown of matching hosts. Scroll down to select. Click on '​x'​ to remove the selected. ​ | |//​Host// ​ |Enter the host, if the element type is '​Host'​. This field is auto-complete so starting to type the name of a host will offer a dropdown of matching hosts. Scroll down to select. Click on '​x'​ to remove the selected. ​ |
 |//​Map// ​ |Select the map, if the element type is '​Map'​. ​ | |//​Map// ​ |Select the map, if the element type is '​Map'​. ​ |
-|//​Triggers// ​ |If the element type is '​Trigger',​ select one or more triggers in the //New triggers// field below and click on //Add//.\\ The order of selected triggers can be changed, but only within the same severity of triggers. ​ |+|//​Triggers// ​  ​|If the element type is '​Trigger',​ select one or more triggers in the //New triggers// field below and click on //Add//.\\ The order of selected triggers can be changed, but only within the same severity of triggers. ​Since Zabbix 3.4.3, multiple trigger selection also affects {HOST.*} macro resolution both in the construction and view modes.\\ // 1 In construction mode// the first displayed {HOST.*} macros will be resolved depending on the first trigger in the list (based on trigger severity).\\ // 2 View mode// depends on the [[manual:​config:​visualisation:​maps:​map#​creating_a_map|Display problems]] parameter in General map attributes.\\ * If //Expand single problem// mode is chosen the first  displayed {HOST.*} macros will be resolved depending on the latest detected problem trigger (not mattering the severity) or the first trigger in the list (in case no problem detected);​\\ * If //Number of problems and expand most critical one// mode is chosen the first displayed ​ {HOST.*} macros will be resolved depending on the trigger severity. ​ \\   |
 |//Host group// ​ |Enter the host group, if the element type is 'Host group'​. This field is auto-complete so starting to type the name of a group will offer a dropdown of matching groups. Scroll down to select. Click on '​x'​ to remove the selected. ​ | |//Host group// ​ |Enter the host group, if the element type is 'Host group'​. This field is auto-complete so starting to type the name of a group will offer a dropdown of matching groups. Scroll down to select. Click on '​x'​ to remove the selected. ​ |
 |//​Application// ​ |You can select an application,​ allowing to only display problems of triggers that belong to the given application.\\ This field is available for host and host group element types, and supported since Zabbix **2.4.0**. ​ | |//​Application// ​ |You can select an application,​ allowing to only display problems of triggers that belong to the given application.\\ This field is available for host and host group element types, and supported since Zabbix **2.4.0**. ​ |