Zabbix Documentation 2.2

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:introduction:whatsnew220

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:introduction:whatsnew220 [2014/11/12 08:12]
martins-v explaining a bit why triggers without events need to be shown
manual:introduction:whatsnew220 [2018/05/10 15:33]
martins-v consistent spelling fix: acknowledgement
Line 73: Line 73:
 Loadable modules, new in Zabbix 2.2, offer a way of extending Zabbix functionality that is more performance-minded than the user parameter option or external checks. In addition to greater performance and the ability to implement any logic, modules have the potential to be developed and shared within the Zabbix community. Loadable modules, new in Zabbix 2.2, offer a way of extending Zabbix functionality that is more performance-minded than the user parameter option or external checks. In addition to greater performance and the ability to implement any logic, modules have the potential to be developed and shared within the Zabbix community.
  
-Supported for Unix-like systems, a loadable module is basically a shared library used by Zabbix server or agent and loaded on startup. To deal with the modules, Zabbix server and agent support two new configuration parameters: ''​LoadModulePath''​ and ''​LoadModule''​. The modules must be located in a directory specified by ''​LoadModulePath''​. It is allowed to include multiple ''​LoadModule''​ parameters.+Supported for Unix-like systems, a loadable module is basically a shared library used by Zabbix server, proxy or agent and loaded on startup. To deal with the modules, Zabbix server, proxy and agent support two new configuration parameters: ''​LoadModulePath''​ and ''​LoadModule''​. The modules must be located in a directory specified by ''​LoadModulePath''​. It is allowed to include multiple ''​LoadModule''​ parameters.
  
 A sample module written in C is included in Zabbix 2.2 under src/​modules/​dummy. It can be used as a template for your own modules. To learn more about the loadable module option, visit the respective documentation [[manual:​config:​items:​loadablemodules|section]]. A sample module written in C is included in Zabbix 2.2 under src/​modules/​dummy. It can be used as a template for your own modules. To learn more about the loadable module option, visit the respective documentation [[manual:​config:​items:​loadablemodules|section]].
Line 83: Line 83:
 Similarly to map labels, only **avg()**, **last()**, **max()** and **min()** functions with seconds as parameter are supported within this macro in graph names. Value mapping is supported as well. Similarly to map labels, only **avg()**, **last()**, **max()** and **min()** functions with seconds as parameter are supported within this macro in graph names. Value mapping is supported as well.
  
-Additionally,​ LLD macros are supported in the parameters of an item key, making it possible to use a macro like {Cisco switch:​ifAlias[{#​SNMPINDEX}].last(0)}+Additionally,​ LLD macros are supported in the parameters of an item key, making it possible to use a macro like {Cisco switch:​ifAlias[{#​SNMPINDEX}].last()}
  
-{HOST.HOST<​1-9>​} macro can be used to reference a host: {{HOST.HOST}:​ifAlias[{#​SNMPINDEX}].last(0)}. As the graph may contain items from several hosts, {HOST.HOST} and {HOST.HOST1} will refer to the first host, {HOST.HOST2} to the second and so on.+{HOST.HOST<​1-9>​} macro can be used to reference a host: {{HOST.HOST}:​ifAlias[{#​SNMPINDEX}].last()}. As the graph may contain items from several hosts, {HOST.HOST} and {HOST.HOST1} will refer to the first host, {HOST.HOST2} to the second and so on.
  
 ==== - Notifications on unsupported items, unknown triggers ==== ==== - Notifications on unsupported items, unknown triggers ====
Line 352: Line 352:
 can be used in the following trigger prototype: can be used in the following trigger prototype:
  
-  {Template_OS_Linux:​vfs.fs.size[{#​FSNAME},​pused].last(0)}>​{#​MY_CUSTOM_MACRO} ​+  {Template_OS_Linux:​vfs.fs.size[{#​FSNAME},​pused].last()}>​{#​MY_CUSTOM_MACRO} ​
  
 To be expanded correctly, the macro must return a numeric value. If the macro value is not numeric or no value is found, a real trigger will not be created. To be expanded correctly, the macro must return a numeric value. If the macro value is not numeric or no value is found, a real trigger will not be created.
  
 +=== - Support of LLD macros in item and trigger descriptions ===
 +
 +Low-level discovery macros can now be used in trigger and item descriptions.
 === - Macros in trigger descriptions === === - Macros in trigger descriptions ===
  
Line 413: Line 416:
 If nothing is selected in //Show selected groups//, then all groups will be displayed, except the ones chosen to hide in the //Hide selected groups// field. If nothing is selected in //Show selected groups//, then all groups will be displayed, except the ones chosen to hide in the //Hide selected groups// field.
  
-=== - Displaying name and surname with acknowledgments ​===+=== - Displaying name and surname with acknowledgements ​===
  
 Previously, only user alias was displayed with acknowledged events - that sometimes did not provide sufficient information,​ especially in systems with many system users. ​ Previously, only user alias was displayed with acknowledged events - that sometimes did not provide sufficient information,​ especially in systems with many system users. ​
  
-To make acknowledgment ​information more informative,​ now a name and surname is also displayed, in the 'alias (name surname)'​ format. The name and surname are taken from the respective (now optional) user configuration fields.+To make acknowledgement ​information more informative,​ now a name and surname is also displayed, in the 'alias (name surname)'​ format. The name and surname are taken from the respective (now optional) user configuration fields.
  
 {{ack_dashboard.png|}} {{ack_dashboard.png|}}
Line 423: Line 426:
 Name and surname now appears in: Name and surname now appears in:
  
-  * acknowledgment ​and action details popup of the Dashboard //Last 20 issues// widget +  * acknowledgement ​and action details popup of the Dashboard //Last 20 issues// widget 
-  * acknowledgment ​and action details popup of the //Host/host group issues// widget in screens +  * acknowledgement ​and action details popup of the //Host/host group issues// widget in screens 
-  * acknowlegdment ​details (accessible from Monitoring -> Triggers)+  * acknowlegdement ​details (accessible from Monitoring -> Triggers)
   * event details   * event details
   * user group member list   * user group member list
Line 466: Line 469:
 //Status of host triggers// and //Status of host group triggers// screen elements have been renamed to //Host issues// and //Host group issues// respectively. ​ //Status of host triggers// and //Status of host group triggers// screen elements have been renamed to //Host issues// and //Host group issues// respectively. ​
  
-Previously, triggers without events would not be displayed in these two widgets, nor in the //Last 20 issues// widget. As a result, sometimes problem triggers would disappear from the widgets when their events got deleted by the Housekeeper. To fix this, now triggers without events are displayed as well.+Previously, triggers without events would not be displayed in these two widgets, nor in the //Last 20 issues// widget. As a result, sometimes problem triggers would disappear from the widgets when their events got deleted by the housekeeper. To fix this, now triggers without events are displayed as well.
  
 === - Hierarchy in global scripts === === - Hierarchy in global scripts ===
Line 588: Line 591:
  
 "​All"​ has been removed as a choice from the trigger severity filter in the frontend, being a redundant duplicate of the "Not classified"​ option. The show_severity=-1 GET parameter, previously returning "​All",​ now defaults to the "Not classified"​ selection. "​All"​ has been removed as a choice from the trigger severity filter in the frontend, being a redundant duplicate of the "Not classified"​ option. The show_severity=-1 GET parameter, previously returning "​All",​ now defaults to the "Not classified"​ selection.
 +
 +=== - Antialiasing in generated graphics ===
 +
 +From now on generated graphs are easier to comprehend due to antialiasing. The change includes support of normal and bold anti-aliased lines lines for graphs, map connectors as well as graph X/Y axis triangles. ​
 +
 +|{{:​manual:​introduction:​graphbefore2.png|}}|{{:​manual:​introduction:​graphafter2.png|}}|
 +|Before the redesign. ​ |After the redesign. ​ |
 +
 ==== - Daemon improvements ==== ==== - Daemon improvements ====
  
Line 616: Line 627:
 === - Value cache for faster access to history data === === - Value cache for faster access to history data ===
  
-To make the calculation of triggers ​expressions,​ calculated/​aggregate items and some macros much faster, a new value cache option is supported by the Zabbix server. ​+To make the calculation of trigger ​expressions,​ calculated/​aggregate items and some macros much faster, a new value cache option is supported by the Zabbix server. ​
  
 This in-memory cache can be used for accessing historical data, instead of making direct SQL calls to the database. If historical values are not present in the cache, the missing values are requested from the database and the cache updated accordingly. This in-memory cache can be used for accessing historical data, instead of making direct SQL calls to the database. If historical values are not present in the cache, the missing values are requested from the database and the cache updated accordingly.
Line 693: Line 704:
   * Spaces are now allowed in the **Server** parameter in the agent daemon configuration file.   * Spaces are now allowed in the **Server** parameter in the agent daemon configuration file.
   * Spaces are now allowed in the **Allowed hosts** field for [[manual:​config:​items:​itemtypes:​trapper|Zabbix trapper items]].   * Spaces are now allowed in the **Allowed hosts** field for [[manual:​config:​items:​itemtypes:​trapper|Zabbix trapper items]].
-  * IP address comparison (for example, for checking incoming connections in Zabbix agent or for Zabbix trapper items) ​will be more efficient if the daemon has been built without IPv6 support. Now it should be on the same performance level as with IPv6 support enabled.+  * IP address comparison (for example, for checking incoming connections in Zabbix agent or for Zabbix trapper items) ​was more efficient if the daemon has been built without IPv6 support. Now it should be on the same performance level as with IPv6 support enabled.
   * Zabbix proxies previously sent availability data for templates when they first started up. While harmless, this was not required. Since 2.2.0, availability data is sent for monitored hosts only, reducing network traffic slightly.   * Zabbix proxies previously sent availability data for templates when they first started up. While harmless, this was not required. Since 2.2.0, availability data is sent for monitored hosts only, reducing network traffic slightly.
-  * Zabbix server previously did not respond to proxy configuration and heartbeat requests that had incorrect ​an proxy name. Starting with 2.2, failure response is returned.+  * Zabbix server previously did not respond to proxy configuration and heartbeat requests that had incorrect proxy name. Starting with 2.2, failure response is returned.
   * Zabbix server now logs response to global script request at **DebugLevel** 4.   * Zabbix server now logs response to global script request at **DebugLevel** 4.
   * Zabbix server previously discarded non-numeric characters in global script request values, and silently closed the connection if any of the required parameters were missing. Since 2.2, non-numeric characters and missing required values result in an error message being returned.   * Zabbix server previously discarded non-numeric characters in global script request values, and silently closed the connection if any of the required parameters were missing. Since 2.2, non-numeric characters and missing required values result in an error message being returned.