Zabbix Documentation 3.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: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
Next revision Both sides next revision
manual:config:visualisation:maps:map [2017/07/28 08:24]
martins-v updating map permission info
manual:config:visualisation:maps:map [2017/10/23 10:02]
natalja.cernohajeva Updated info about resolution of {HOST.*} macro if multiple triggers are selected (copied from 4.0 version)
Line 1: Line 1:
-==== - #1 Configuring a network map ====+==== 1 Configuring a network map ====
  
 === Overview === === Overview ===
Line 13: Line 13:
 Maps are managed in //​Monitoring//​ -> //​[[manual:​web_interface:​frontend_sections:​monitoring:​maps|Maps]]//,​ where they can be configured, managed and viewed. In the monitoring view you can click on the icons and take advantage of the links to some scripts and URLs.  Maps are managed in //​Monitoring//​ -> //​[[manual:​web_interface:​frontend_sections:​monitoring:​maps|Maps]]//,​ where they can be configured, managed and viewed. In the monitoring view you can click on the icons and take advantage of the links to some scripts and URLs. 
  
-All users in Zabbix ​(including non-admin userscan create network mapsMaps have an owner - the user who created them.+Network maps are based on vector graphics ​(SVGsince Zabbix 3.4.
  
-Maps can be made public or private. ​Public ​maps are visible to all users, although the user must have read access to at least one map element. Map elements that the user does not have read permission to have a greyed out icon and all textual information on the element is hidden. To add an element to the map the user must also have at least read permission to it.+=== Public and private maps ===
  
-Private maps are visible only to their owner and the users/user groups the map is shared with by the owner. Regular ​(non-Super admin) ​users can only share with the groups and users they are member ofAdmin level users can see private ​maps regardless of being the owner or belonging to the shared user list+All users in Zabbix ​(including ​non-admin ​users) can create network maps. Maps have an owner - the user who created themMaps can be made public or private. ​
  
-Still, to see the map the user must have read access to at least one map element. Map elements that the user does not have read permission to have a greyed out icon and all textual information on the element is hidden.+  * //Public// maps are visible to all usersalthough ​to see it the user must have read access to at least one map element.
  
-Network ​maps are based on vector graphics ​(SVGsince Zabbix 3.4.+  * //​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.  
 + 
 +=== 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. 
 + 
 +To add an element to the map the user must also have at least read permission to it.
  
 === Creating a map === === Creating a map ===
Line 48: Line 64:
 |//Mark elements on trigger status change// ​ |A recent change of trigger status (recent problem or resolution) will be highlighted with markers (inward-pointing red triangles) on the three sides of the element icon that are free of the label. Markers are displayed for 30 minutes.| |//Mark elements on trigger status change// ​ |A recent change of trigger status (recent problem or resolution) will be highlighted with markers (inward-pointing red triangles) on the three sides of the element icon that are free of the label. Markers are displayed for 30 minutes.|
 |//Display problems// ​ |Select how problems are displayed with a map element:\\ **Expand single problem** - if a map element has one single problem, the problem (trigger) name is displayed\\ **Number of problems** - the total number of problems is displayed\\ **Number of problems and expand most critical one** - problem (trigger) name is displayed for the most critical one and the total number of problems is displayed. 'Most critical'​ is determined based on:\\ //For trigger map element// - trigger severity and trigger position in the trigger list;\\ //For other map elements// - trigger severity and trigger ID.  | |//Display problems// ​ |Select how problems are displayed with a map element:\\ **Expand single problem** - if a map element has one single problem, the problem (trigger) name is displayed\\ **Number of problems** - the total number of problems is displayed\\ **Number of problems and expand most critical one** - problem (trigger) name is displayed for the most critical one and the total number of problems is displayed. 'Most critical'​ is determined based on:\\ //For trigger map element// - trigger severity and trigger position in the trigger list;\\ //For other map elements// - trigger severity and trigger ID.  |
-|//Advanced labels// ​ |If you check this box you will be able to define separate label types for separate element types.|+|//Advanced labels// ​ |If you check this box you will be able to define separate label types for separate element types. ​ |
 |//Icon label type// ​ |Label type used for icons:\\ **Label** - icon label\\ **IP address** - IP address\\ **Element name** - element name (for example, host name)\\ **Status only** - status only (OK or PROBLEM)\\ **Nothing** - no labels are displayed| |//Icon label type// ​ |Label type used for icons:\\ **Label** - icon label\\ **IP address** - IP address\\ **Element name** - element name (for example, host name)\\ **Status only** - status only (OK or PROBLEM)\\ **Nothing** - no labels are displayed|
 |//Icon label location// ​ |Label location in relation to the icon:\\ **Bottom** - beneath the icon\\ **Left** - to the left\\ **Right** - to the right\\ **Top** - above the icon| |//Icon label location// ​ |Label location in relation to the icon:\\ **Bottom** - beneath the icon\\ **Left** - to the left\\ **Right** - to the right\\ **Top** - above the icon|
Line 81: Line 97:
  
 ^Parameter^Description^ ^Parameter^Description^
-|//​Type// ​ |Type of the element:\\ **Host** - icon representing status of all triggers of the selected host\\ **Map** - icon representing status of all elements of a map\\ **Trigger** - icon representing status of one or more triggers\\ **Host group** - icon representing status of all triggers of all hosts belonging to the selected group\\ **Image** - an icon, not linked to any resource ​ |+|//​Type// ​ |Type of the element:\\ **Host** - icon representing status of all triggers of the selected host\\ **Map** - icon representing status of all elements of a map\\ **Trigger** - icon representing status of one or more triggers\\ ​Note that, starting with Zabbix 3.4.3, if multiple triggers are selected, {HOST.*} macros will be resolved based on the first trigger in the list (which is based on trigger priority).\\ ​**[[manual:​config:​visualisation:​maps:​host_groups|Host group]]** - icon representing status of all triggers of all hosts belonging to the selected group\\ **Image** - an icon, not linked to any resource ​ |
 |//​Label// ​ |Icon label, any string.\\ [[manual:​config:​macros|Macros]] and multi-line strings can be used in labels. ​ | |//​Label// ​ |Icon label, any string.\\ [[manual:​config:​macros|Macros]] and multi-line strings can be used in labels. ​ |
 |//Label location// ​ |Label location in relation to the icon:\\ **Default** - map's default label location\\ **Bottom** - beneath the icon\\ **Left** - to the left\\ **Right** - to the right\\ **Top** - above the icon  | |//Label location// ​ |Label location in relation to the icon:\\ **Default** - map's default label location\\ **Bottom** - beneath the icon\\ **Left** - to the left\\ **Right** - to the right\\ **Top** - above the icon  |
 |//​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**. ​ |
Line 167: Line 183:
 To add a line, click on //Add// next to Shape. A new shape will appear at the top left corner of the map. Select it and click on //Line// in the editing form to change the shape into a line. Then adjust line properties, such as line type, width, colour, etc. To add a line, click on //Add// next to Shape. A new shape will appear at the top left corner of the map. Select it and click on //Line// in the editing form to change the shape into a line. Then adjust line properties, such as line type, width, colour, etc.
  
-{{:​manual:​config:​visualisation:​map_line.png}}+{{:​manual:​config:​visualisation:​map_line.png?600}}
  
 === Ordering shapes and lines === === Ordering shapes and lines ===