[comment]: # ({aa5e1cff-e452fbf7}) # 8 Maps [comment]: # ({/aa5e1cff-e452fbf7}) [comment]: # ({391c7362-20a11f83}) #### Overview In the *Monitoring → Maps* section you can configure, manage and view [network maps](/fr/manual/config/visualisation/maps). When you open this section, you will either see the last map you accessed or a listing of all maps you have access to. Map listing can be filtered by name. Since Zabbix 3.0 all maps can be either public or private. Public maps are available to all users, while private maps are accessible only to their owner and the users the map is shared with. [comment]: # ({/391c7362-20a11f83}) [comment]: # ({1245e8f5-c1cb6946}) #### Map listing ![](../../../../../assets/en/manual/web_interface/map_list.png){width="600"} Displayed data: |Column|Description| |------|-----------| |*Name*|Name of the map. Click on the name to [view](/manual/web_interface/frontend_sections/monitoring/maps#viewing_maps) the map.| |*Width*|Map width is displayed.| |*Height*|Map height is displayed.| |*Actions*|Two actions are available:
**Properties** - edit general map [properties](/manual/config/visualization/maps/map#creating_a_map)
**Constructor** - access the grid for adding [map elements](/manual/config/visualization/maps/map#adding_elements)| To [configure](/manual/config/visualization/maps/map#creating_a_map) a new map, click on the *Create map* button in the top right-hand corner. To import a map from an XML file, click on the *Import* button in the top right-hand corner. The user who imports the map will be set as its owner. Two buttons below the list offer some mass-editing options: - *Export* - export the maps to an XML file - *Delete* - delete the maps To use these options, mark the checkboxes before the respective maps, then click on the required button. [comment]: # ({/1245e8f5-c1cb6946}) [comment]: # ({35619569-1d312fad}) #### Viewing maps To view a map, click on its name in the list of all maps. ![](../../../../../assets/en/manual/web_interface/maps.png){width="600"} You can use the dropdown in the map title bar to select the lowest severity level of the problem triggers to display. The severity marked as *default* is the level set in map configuration. If the map contains a submap, navigating to the submap will retain the higher-level map severity. [comment]: # ({/35619569-1d312fad}) [comment]: # ({bb7cb0af-a9b8dc1b}) ##### Icon highlighting If a map element is in problem status, it is highlighted with a round circle. The fill colour of the circle corresponds to the severity colour of the problem trigger. Only problems on or above the selected severity level will be displayed with the element. If all problems are acknowledged, a thick green border around the circle is displayed. Additionally, a host in [maintenance](/fr/manual/maintenance) is highlighted with an orange, filled square and a disabled (not-monitored) host is highlighted with a grey, filled square. Highlighting is displayed if the *Icon highlighting* check-box is marked in map [configuration](/manual/config/visualization/maps/map#creating_a_map). [comment]: # ({/bb7cb0af-a9b8dc1b}) [comment]: # ({ca5ce6c0-f6436c14}) ##### Recent change markers Inward pointing red triangles around an element indicate a recent trigger status change - one that's happened within the last 30 minutes. These triangles are shown if the *Mark elements on trigger status change* check-box is marked in map [configuration](/fr/manual/config/visualisation/maps/map#creating_a_map). [comment]: # ({/ca5ce6c0-f6436c14}) [comment]: # ({0e0ddb36-89ad8a4d}) ##### Links Clicking on a map element opens a menu with some available links. [comment]: # ({/0e0ddb36-89ad8a4d}) [comment]: # ({72e853d5-0e0ddb36}) ##### Controls Three control buttons are available in the title bar: - ![](../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/edit_map.png) - go to map constructor to edit the map content - ![](../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/add_to_fav.png) - add map to the favourites widget in the [Dashboard](dashboard) - ![](../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/full_window.png) - use the full browser window to display the map [comment]: # ({/72e853d5-0e0ddb36}) [comment]: # ({15da840f-8bceddc5}) ##### Readable summary in maps A hidden "aria-label" property is available allowing map information to be read with a screen reader. Both general map description and individual element description is available, in the following format: - for map description: `, <* of * items in problem state>, <* problems in total>.` - for describing one element with one problem: `, Status , , .` - for describing one element with multiple problems: `, Status , , <* problems>.` - for describing one element without problems: `, Status , .` For example, this description is available: 'Local network, 1 of 6 elements in problem state, 1 problem in total. Host, Status problem, My host, Free disk space is less than 20% on volume \/. Host group, Status ok, Virtual servers. Host, Status ok, Server 1. Host, Status ok, Server 2. Host, Status ok, Server 3. Host, Status ok, Server 4. ' for the following map: ![](../../../../../assets/en/manual/web_interface/map_aria_label.png){width="600"} [comment]: # ({/15da840f-8bceddc5}) [comment]: # ({70e40daf-15da840f}) ##### Referencing a network map Network maps can be referenced by both `sysmapid` and `mapname` GET parameters. For example, http://zabbix/zabbix/maps.php?mapname=Local%20network will open the map with that name (Local network). If both `sysmapid` (map ID) and `mapname` (map name) are specified, `mapname` has higher priority. [comment]: # ({/70e40daf-15da840f}) [comment]: # ({c4642e16-c4642e16}) ##### Referencing a network map Network maps can be referenced by both `sysmapid` and `mapname` GET parameters. For example, http://zabbix/zabbix/zabbix.php?action=map.view&mapname=Local%20network will open the map with that name (Local network). If both `sysmapid` (map ID) and `mapname` (map name) are specified, `mapname` has higher priority. [comment]: # ({/c4642e16-c4642e16})