Zabbix Documentation 2.0

2.23.04.04.2 (current)In development:4.4 (devel)Unsupported:1.82.02.43.23.4

User Tools

Site Tools


manual:introduction:whatsnew200

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
manual:introduction:whatsnew200 [2014/09/25 14:41]
sasha Page moved from 2.0:manual:introduction:whatsnew200 to manual:introduction:whatsnew200
manual:introduction:whatsnew200 [2014/09/25 15:20] (current)
192.168.3.21 Links adapted because of a move operation
Line 5: Line 5:
 === - Low level discovery === === - Low level discovery ===
  
-[[:2.0/manual/discovery/low_level_discovery|Low level discovery documentation]]+[[manual:discovery:low_level_discovery|Low level discovery documentation]]
  
 == - Network interface discovery == == - Network interface discovery ==
Line 37: Line 37:
 === - Automatic inventory data collection === === - Automatic inventory data collection ===
  
-Host inventory now can be populated [[:2.0/manual/config/hosts/inventory#​building_inventory|automatically]]. Items have a property that allows to store their value in any of the inventory fields if inventory is set to //​Automatic//​ mode.+Host inventory now can be populated [[manual:config:hosts:inventory#​building_inventory|automatically]]. Items have a property that allows to store their value in any of the inventory fields if inventory is set to //​Automatic//​ mode.
  
 === - WEB monitoring by Zabbix proxies === === - WEB monitoring by Zabbix proxies ===
Line 58: Line 58:
 === - Direct JMX monitoring support === === - Direct JMX monitoring support ===
  
-Ability to monitor JMX without deploying additional software has been introduced in the form of a [[:2.0/manual/config/items/itemtypes/jmx_monitoring|Java gateway]].+Ability to monitor JMX without deploying additional software has been introduced in the form of a [[manual:config:items:itemtypes:jmx_monitoring|Java gateway]].
  
 === - Visible host name === === - Visible host name ===
Line 66: Line 66:
 === - SNMP trap monitoring === === - SNMP trap monitoring ===
  
-[[:2.0/manual/config/items/itemtypes/snmptrap|SNMP trap item documentation]].+[[manual:config:items:itemtypes:snmptrap|SNMP trap item documentation]].
  
 ==== - Frontend improvements ==== ==== - Frontend improvements ====
Line 97: Line 97:
 If an outdated browser will be detected by Zabbix frontend, a warning page will be displayed. It will link to download pages for multiple more recent browsers. User would not be blocked from accessing Zabbix frontend, though - that would still be possible via the link in the lower right corner. If an outdated browser will be detected by Zabbix frontend, a warning page will be displayed. It will link to download pages for multiple more recent browsers. User would not be blocked from accessing Zabbix frontend, though - that would still be possible via the link in the lower right corner.
  
-{{:​2.0:​manual:​introduction:​browser_warning.png|}}+{{browser_warning.png|}}
  
 === - SQLite supported by frontend === === - SQLite supported by frontend ===
Line 142: Line 142:
 For example, here two URLs have been defined on the element (host) level: For example, here two URLs have been defined on the element (host) level:
  
-{{:​2.0:​manual:​introduction:​multiple_element_urls.png|}}+{{multiple_element_urls.png|}}
  
 On the map level, URLs can be defined for all element types. Here, URL is defined for each available element type: On the map level, URLs can be defined for all element types. Here, URL is defined for each available element type:
  
-{{:​2.0:​manual:​introduction:​multiple_element_urls_map.png?​600|}}+{{multiple_element_urls_map.png?​600|}}
  
 Of course, it is also possible to add multiple URLs for the same element type. Of course, it is also possible to add multiple URLs for the same element type.
Line 152: Line 152:
 When these URLs have been configured, in the monitoring section clicking on a map element will list them (by name) in the popup menu. If the element has it's own URLs and there are map level URLs for its type defined, they will be combined in the same menu: When these URLs have been configured, in the monitoring section clicking on a map element will list them (by name) in the popup menu. If the element has it's own URLs and there are map level URLs for its type defined, they will be combined in the same menu:
  
-{{:​2.0:​manual:​introduction:​multiple_element_urls_popup.png|}}+{{multiple_element_urls_popup.png|}}
  
 From the already existing macros, in map URLs macro {TRIGGER.ID} can be used. From the already existing macros, in map URLs macro {TRIGGER.ID} can be used.
Line 169: Line 169:
 In previous versions, one could select map label type for all map elements in the map. Starting with 2.0.0, it is possible to enable //Advanced labels// feature per map and choose map element label per element type - image, trigger, host, host group and map. In previous versions, one could select map label type for all map elements in the map. Starting with 2.0.0, it is possible to enable //Advanced labels// feature per map and choose map element label per element type - image, trigger, host, host group and map.
  
-{{:​2.0:​manual:​introduction:​map_element_labels.png|}}+{{map_element_labels.png|}}
  
 ** Displaying hosts from a host group ** ** Displaying hosts from a host group **
Line 179: Line 179:
 Automatic icon selection for host type map elements has been added. It utilises values from host inventory fields to select icon for map elements. Automatic icon selection for host type map elements has been added. It utilises values from host inventory fields to select icon for map elements.
  
-Icon maps are configured in //​Administration -> General -> [[:2.0/manual/web_interface/frontend_sections/administration/general#​icon_mapping|Icon maps]]//. Each icon map has a unique name, default icon and a list of mappings. Each mapping has a match order, expression for matching (PCRE regular expression or Zabbix expression),​ icon and reference to an inventory field. Icon map can be assigned to a map in the map configuration form, and overridden on map element level.+Icon maps are configured in //​Administration -> General -> [[manual:web_interface:frontend_sections:administration:general#​icon_mapping|Icon maps]]//. Each icon map has a unique name, default icon and a list of mappings. Each mapping has a match order, expression for matching (PCRE regular expression or Zabbix expression),​ icon and reference to an inventory field. Icon map can be assigned to a map in the map configuration form, and overridden on map element level.
  
 When deciding on which icon should be used, regular expression will be matched against specified inventory field. Order in which mappings are tried depends on match order. When deciding on which icon should be used, regular expression will be matched against specified inventory field. Order in which mappings are tried depends on match order.
Line 204: Line 204:
   * Only one endpoint of a link may be changed when editing a link. Endpoint that is currently selected can not be changed in this view anymore. Additionally,​ endpoints are sorted by type in the dropdown   * Only one endpoint of a link may be changed when editing a link. Endpoint that is currently selected can not be changed in this view anymore. Additionally,​ endpoints are sorted by type in the dropdown
  
-{{:​2.0:​manual:​introduction:​link_endpoint_dropdown.png|}}+{{link_endpoint_dropdown.png|}}
  
 === - Customisable trigger severity names and colours === === - Customisable trigger severity names and colours ===
Line 224: Line 224:
 Events from //​Monitoring -> Events// page can now be exported to a CSV file by using a button in the upper right corner. Events from //​Monitoring -> Events// page can now be exported to a CSV file by using a button in the upper right corner.
  
-{{:​2.0:​manual:​introduction:​event_export_to_csv.png?​600|}}+{{event_export_to_csv.png?​600|}}
  
 Only currently visible events are exported. Only currently visible events are exported.
Line 234: Line 234:
 User scripts that can be configured on the frontend in //​Administration -> Scripts// can now display a confirmation message before being executed. A custom message confirmation message can be entered by the administrator. This feature should be especially useful with potentially dangerous operations (like a reboot script) or ones that might take a long time. User scripts that can be configured on the frontend in //​Administration -> Scripts// can now display a confirmation message before being executed. A custom message confirmation message can be entered by the administrator. This feature should be especially useful with potentially dangerous operations (like a reboot script) or ones that might take a long time.
  
-{{:​2.0:​manual:​introduction:​script_confirmation_config.png?​500|}}+{{script_confirmation_config.png?​500|}}
  
 Confirmation can be tested in the configuration form. In that case, //Execute// button is disabled. Confirmation can be tested in the configuration form. In that case, //Execute// button is disabled.
  
-{{:​2.0:​manual:​introduction:​script_confirmation_popup_test.png|}}+{{script_confirmation_popup_test.png|}}
  
 **Ability to specify script type** **Ability to specify script type**
Line 244: Line 244:
 Before, if a user script would have to be an IPMI command, it had to follow a syntax of //IPMI <​command>//​. Starting with Zabbix 2.0, it is an option in the script editing form. Before, if a user script would have to be an IPMI command, it had to follow a syntax of //IPMI <​command>//​. Starting with Zabbix 2.0, it is an option in the script editing form.
  
-{{:​2.0:​manual:​introduction:​script_type_dropdown.png|}}+{{script_type_dropdown.png|}}
  
 **Ability to execute scripts on Zabbix agent** **Ability to execute scripts on Zabbix agent**
  
-Before Zabbix 2.0, user scripts could be executed on the Zabbix server only. Starting with 2.0, a script can be configured to be executed on the agent instead. For this feature to work, agent must be [[:2.0/manual/appendix/config/zabbix_agentd|configured to allow remote commands]].+Before Zabbix 2.0, user scripts could be executed on the Zabbix server only. Starting with 2.0, a script can be configured to be executed on the agent instead. For this feature to work, agent must be [[manual:appendix:config:zabbix_agentd|configured to allow remote commands]].
  
-{{:​2.0:​manual:​introduction:​script_execute_on.png|}}+{{script_execute_on.png|}}
  
 === - Media type improvements === === - Media type improvements ===
Line 258: Line 258:
 In media type configuration screen it's now possible to view and access actions that directly refer to this media type (it's selected in the //Send only to// dropdown). When sorting by that column, entries are only sorted by whether they are referenced, actions referencing media types do not influence the sort order. It is possible to go directly to action configuration from this page as well. In media type configuration screen it's now possible to view and access actions that directly refer to this media type (it's selected in the //Send only to// dropdown). When sorting by that column, entries are only sorted by whether they are referenced, actions referencing media types do not influence the sort order. It is possible to go directly to action configuration from this page as well.
  
-{{:​2.0:​manual:​introduction:​media_types_used_in_actions.png?​600|}}+{{media_types_used_in_actions.png?​600|}}
  
 **Enabling and disabling media types** **Enabling and disabling media types**
Line 265: Line 265:
 For graphs with many items added, legend could grow pretty huge, and there might be other reasons why somebody might want to hide the legend. Starting with Zabbix 2.0.0, that is possible for custom graphs with a simple checkbox: For graphs with many items added, legend could grow pretty huge, and there might be other reasons why somebody might want to hide the legend. Starting with Zabbix 2.0.0, that is possible for custom graphs with a simple checkbox:
  
-{{:​2.0:​manual:​introduction:​disabling_graph_legend.png?​600|}}+{{disabling_graph_legend.png?​600|}}
  
 === - Improved popup placement === === - Improved popup placement ===
Line 285: Line 285:
 Triggers element (by host or by host group) in screens now can be sorted by severity, host or date. Triggers element (by host or by host group) in screens now can be sorted by severity, host or date.
  
-{{:​2.0:​manual:​introduction:​screen_element_triggers_sorting.png|}}+{{screen_element_triggers_sorting.png|}}
  
 https://​support.zabbix.com/​browse/​ZBXNEXT-746 https://​support.zabbix.com/​browse/​ZBXNEXT-746
Line 366: Line 366:
   * IP as the first parameter is not ignored anymore, thus it is possible to specify different DNS server than localhost   * IP as the first parameter is not ignored anymore, thus it is possible to specify different DNS server than localhost
   * Both items gained ability to specify timeout and retry count (not supported on Windows)   * Both items gained ability to specify timeout and retry count (not supported on Windows)
-  * **net.dns** gained support for specifying DNS record type like //A//, //CNAME// and //MX// (**net.dns.record** already supported that). See [[:2.0/manual/config/items/itemtypes/zabbix_agent|item documentation]] for more information+  * **net.dns** gained support for specifying DNS record type like //A//, //CNAME// and //MX// (**net.dns.record** already supported that). See [[manual:config:items:itemtypes:zabbix_agent|item documentation]] for more information
  
 **net.tcp.service** and **net.tcp.service.perf** now support https and telnet. **net.tcp.service** and **net.tcp.service.perf** now support https and telnet.
Line 376: Line 376:
 **system.cpu.load** now accepts //percpu// as the first parameter - if specified, total load divided by online CPU count is returned (default is still //all// and returns normal load value) **system.cpu.load** now accepts //percpu// as the first parameter - if specified, total load divided by online CPU count is returned (default is still //all// and returns normal load value)
  
-**vm.memory.size** now supports more modes for various platforms. See [[:2.0/manual/appendix/items/supported_by_platform|supported by platform]] and [[:2.0/manual/appendix/items/vm.memory.size_params|vm.memory.size parameters]] pages for more information.+**vm.memory.size** now supports more modes for various platforms. See [[manual:appendix:items:supported_by_platform|supported by platform]] and [[manual:appendix:items:vm.memory.size_params|vm.memory.size parameters]] pages for more information.
  
 == - Skipping older data in log monitoring == == - Skipping older data in log monitoring ==
Line 389: Line 389:
 == - Simple check format changed == == - Simple check format changed ==
  
-The format of [[:2.0:manual:​config:​items:​itemtypes:​simple_checks|simple checks]] has been changed. The possibility of using IP addresses in simple checks has been added. The upgrade process converts all existing simple checks.+The format of [[manual:​config:​items:​itemtypes:​simple_checks|simple checks]] has been changed. The possibility of using IP addresses in simple checks has been added. The upgrade process converts all existing simple checks.
  
 == - Ability to send empty strings == == - Ability to send empty strings ==
Line 397: Line 397:
 == - External check parameter changes == == - External check parameter changes ==
  
-[[:2.0/manual/config/items/itemtypes/external|External check]] parameter handling was changed. Previously, only one parameter was accepted. Starting with Zabbix 2.0, the key syntax conforms to other types of items and multiple comma-separated parameters may be passed.+[[manual:config:items:itemtypes:external|External check]] parameter handling was changed. Previously, only one parameter was accepted. Starting with Zabbix 2.0, the key syntax conforms to other types of items and multiple comma-separated parameters may be passed.
  
 Additionally,​ the hardcoded first parameter {HOST.CONN} for external checks has been removed and now external check parameters may be fully customised. Upgrade process adds this macro as a first parameter to all existing external checks. Additionally,​ the hardcoded first parameter {HOST.CONN} for external checks has been removed and now external check parameters may be fully customised. Upgrade process adds this macro as a first parameter to all existing external checks.
Line 423: Line 423:
   * system.sw.packages[package,​manager,​short|full] - default is [all,​all,​full],​ package is regex   * system.sw.packages[package,​manager,​short|full] - default is [all,​all,​full],​ package is regex
  
-A **status** item has been removed as it was not easy to use and understand. Instead, a new [[2.0:manual:​config:​items:​itemtypes:​internal|internal item]] - **zabbix[host,<​type>,​available]** has been added. It allows to properly monitor host availability by each of states - Zabbix agent, SNMP, IPMI, JMX - and returns values for available, unavailable and unknown. ​+A **status** item has been removed as it was not easy to use and understand. Instead, a new [[manual:​config:​items:​itemtypes:​internal|internal item]] - **zabbix[host,<​type>,​available]** has been added. It allows to properly monitor host availability by each of states - Zabbix agent, SNMP, IPMI, JMX - and returns values for available, unavailable and unknown. ​
 The database upgrade process **doesn'​t convert** all existing '​status'​ keys and associated triggers to the new syntax, so they have to be converted manually. The database upgrade process **doesn'​t convert** all existing '​status'​ keys and associated triggers to the new syntax, so they have to be converted manually.
  
Line 473: Line 473:
  
 == - Database creation == == - Database creation ==
-<note important>​Order of [[2.0:manual:​installation:​install|database file import]] has been changed - images must be imported before **data.sql** now.</​note>​+<note important>​Order of [[manual:​installation:​install|database file import]] has been changed - images must be imported before **data.sql** now.</​note>​
  
 === - Improved active agent auto-registration === === - Improved active agent auto-registration ===
Line 657: Line 657:
 === - Monitoring of files larger than 2GB === === - Monitoring of files larger than 2GB ===
  
-While Zabbix did offer monitoring of files larger than 2GB before, this support was not consistent - it varied by platform and by item. Since 2.0, support for files exceeding 2GB is available also on 32-bit systems in all components, including tasks like logfile monitoring, file size monitoring etc. See [[:2.0/manual/appendix/items/large_file_support|large file support]] section for more information.+While Zabbix did offer monitoring of files larger than 2GB before, this support was not consistent - it varied by platform and by item. Since 2.0, support for files exceeding 2GB is available also on 32-bit systems in all components, including tasks like logfile monitoring, file size monitoring etc. See [[manual:appendix:items:large_file_support|large file support]] section for more information.
 ==== See also ==== ==== See also ====
  
   - [[http://​blog.zabbix.com/​multiple-servers-for-active-agent-sure|Differences in the Zabbix agent configuration for active and passive checks starting from version 2.0.0]]   - [[http://​blog.zabbix.com/​multiple-servers-for-active-agent-sure|Differences in the Zabbix agent configuration for active and passive checks starting from version 2.0.0]]