Zabbix Documentation 5.0

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:whatsnew500

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Previous revision
Next revision Both sides next revision
manual:introduction:whatsnew500 [2019/10/31 11:04]
manual:introduction:whatsnew500 [2020/02/24 10:24]
martins-v more precise wording
Line 1: Line 1:
 +===== 5 What's new in Zabbix 5.0.0 =====
  
 +<note important>​Zabbix 5.0.0 is not released yet.</​note>​
 +
 +=== Test item from UI ===
 +
 +In previous Zabbix versions it was difficult to tell if a newly-configured [[:​manual/​config/​items|item]] was configured correctly or not. For that you needed to wait until the item tried to gather some data.
 +
 +In the new version it is possible to test the item (template item, item prototype, low-level discovery rule) from the user interface even before saving and, if configured correctly, get a real value in return. ​
 +
 +Item testing is not supported for active items and some simple checks (''​icmpping*'',​ ''​vmware.*''​ items).
 +
 +To test the item, click on the //Test// button at the bottom of the item configuration form. 
 +
 +{{:​manual:​config:​items:​item_test_button.png|}}
 +
 +The item testing form has fields for the required host parameters (host address, port, proxy name/no proxy). These fields are context aware:
 +
 +  * The values are pre-filled when possible, i.e. for items requiring an agent, by taking the information from the selected agent interface of the host
 +  * The values have to be filled manually for template items
 +  * The fields are disabled when not needed in the context of the item type (e.g. the host address field is disabled for calculated and aggregate items, the proxy field is disabled for calculated items)
 +
 +To test the item, click on //Get value//. If the value is retrieved successfully,​ it will fill the //Value// field.
 +
 +{{:​manual:​introduction:​item_test_highlighted.png?​600|}}
 +
 +A successfully retrieved value from host can also be used to test the preprocessing steps. ​
 +
 +In fact, the item testing form is an extension of the preprocessing testing form already known in recent Zabbix versions. So if previously you could test preprocessing steps only against a hypothetical input value, now it is also possible to test preprocessing against a real test value just received.
 +
 +To test the preprocessing steps against the real value, click on //Get value and test//.
 +
 +See also:
 +
 +  * [[:​manual/​config/​items/​item#​testing|Testing an item]]
 +  * [[:​manual/​config/​items/​preprocessing#​testing|Testing preprocessing steps]]
 +
 +== Execute now ==
 +
 +In a related development the //Check now// [[:​manual/​config/​items/​check_now|option]] has been renamed to //Execute now//.
 +
 +=== IPMI sensor discovery ===
 +
 +A new ''​ipmi.get''​ IPMI item has been added that returns a JSON with IPMI-sensor related information. This item can be used for the [[:​manual/​discovery/​low_level_discovery/​ipmi_sensors#​overview|discovery of IPMI sensors]].
 +
 +=== Item key limit raised ===
 +
 +The maximum allowed length of an item key has been raised from 256 to 2048 characters.
 +
 +=== Restricting agent checks ===
 +
 +It is possible to restrict checks on the agent side by creating a whitelist or blacklist of allowed item keys.
 +
 +Whitelist/​blacklist is created using a combination of two new agent [[:​manual/​appendix/​config/​zabbix_agentd|configuration]] parameters:
 +
 +  * ''​AllowKey=<​pattern>''​ - which checks are allowed; <​pattern>​ is specified using a wildcard (*) expression
 +  * ''​DenyKey=<​pattern>''​ - which checks are denied; <​pattern> ​ is specified using a wildcard (*) expression
 +
 +See also: [[:​manual/​appendix/​config/​restrict_checks|Restricting agent checks]]
 +
 +=== Stronger cryptography for passwords ===
 +
 +A stronger bcrypt cryptography is now used for hashing user passwords instead of MD5. The change to the stronger cryptography after the upgrade is automatic, i.e. no effort on the user side is required. Note that passwords longer than 72 characters will be truncated.
 +
 +=== Using HTTP proxy in webhooks ===
 +
 +It is now possible to specify an HTTP proxy when configuring a [[:​manual/​config/​notifications/​media/​webhook|webhook]]. The new HTTPProxy parameter is listed in the webhook parameter list by default with an empty value. ​
 +
 +When specifying the proxy value the same functionality as in the item configuration [[:​manual/​config/​items/​itemtypes/​http#​configuration|HTTP proxy]] field is supported.
 +
 +=== Mass unlinking of templates ===
 +
 +It is now possible to mass unlink templates when using host or template mass update:
 +
 +{{:​manual:​introduction:​hosts_mass_unlink.png|}}
 +
 +See also:
 +
 +  * Host mass [[:​manual/​config/​hosts/​hostupdate|update]]
 +  * Template mass [[:​manual/​config/​templates/​mass|update]]
 +
 +=== Default messages for each media type ===
 +
 +It is now possible to specify default message templates for each event type when defining [[:​manual/​config/​notifications/​media|Media types]]
 +
 +{{:​manual:​introduction:​msg_templates.png?​600|}}
 +
 +==== Macros ====
 +
 +=== Updated macros ===
 +
 +  * {HOST.ID} is now supported in trigger-based notifications and commands, problem update notifications and internal notifications. ​
 +
 +==== Databases ====
 +
 +=== Support of IBM DB2 dropped ===
 +
 +The IBM DB2 database is no longer supported by Zabbix.
 +
 +=== Minimum required versions updated ===
 +
 +The minimum required versions for supported [[:​manual/​installation/​requirements#​Software|databases]] now are:
 +
 +  * MySQL 5.5.62
 +  * MariaDB 10.0.37
 +  * PostgreSQL 9.2.24
 +  * Oracle 11.2
 +
 +==== Frontend ====
 +
 +=== Minimum required PHP version ===
 +
 +The minimum required PHP version has been upped from 5.4.0 to 7.2.0.
 +
 +=== Support of Internet Explorer 11 dropped ===
 +
 +Microsoft Internet Explorer 11 is no longer supported by Zabbix.
 +
 +=== Page selection dropdown integrated into headings ===
 +
 +Some frontend sections in Zabbix may display a different page depending on user selection. For example, //​Administration//​ -> //General// may display twelve different pages. ​
 +
 +Previously, the page selection was made in a rather small, easy-to-miss dropdown located in the top right corner of the page. Now that selection has been integrated into the headings on the left.
 +
 +|{{:​manual:​introduction:​adm_general_new.png|}} ​ |
 +|In Zabbix 5.0.  |
 +|{{:​manual:​introduction:​adm_general_old.png?​600|}} ​ |
 +|Before Zabbix 5.0.  |
 +
 +This change affects the following sections:
 +
 +  * //​Monitoring//​ -> //​Overview//​
 +  * //​Monitoring//​ -> //Screens//
 +  * //​Configuration//​ -> //Actions//
 +  * //​Administration//​ -> //General//
 +  * //​Administration//​ -> //Queue//
 +=== Detail editing as popup window ===
 +
 +In several configuration sections of Zabbix frontend detail editing is now opened as a popup window. This is implemented for:
 +
 +  * Action conditions
 +  * Global correlation conditions
 +  * Action operation details ​
 +    * in the [[:​manual/​config/​notifications/​action/​operation#​configuring_an_operation|Operations]],​ [[:​manual/​config/​notifications/​action/​recovery_operations#​configuring_a_recovery_operation|Recovery operations]] and [[:​manual/​config/​notifications/​action/​acknowledgement_operations#​configuring_an_update_operation|Update operations]] tabs
 +  * Maintenance period details ​
 +    * in the [[:​manual/​maintenance#​configuration|Periods]] tab
 +  * Discovery rule details
 +    * see discovery [[:​manual/​discovery/​network_discovery/​rule#​rule_attributes|check]] editing
 +
 +In many cases this change allows to de-clutter the interface of having to configure too many options in one screen. For example, details of an action operation are now opened in a separate popup window.
 +
 +{{:​manual:​introduction:​oper_details_new.png?​600|}}
 +
 +=== New filtering options for dashboard widgets ===
 +Dashboard widgets [[:​manual/​web_interface/​frontend_sections/​monitoring/​dashboard/​widgets#​problems_by_severity|Problems by severity]] and [[:​manual/​web_interface/​frontend_sections/​monitoring/​dashboard/​widgets#​problem_hosts|Problem hosts]] now support filtering problems by tags. 
 +
 +=== Filtering problems by severities in Monitoring->​Problems ===
 +Problems displayed in the //​Monitoring->​ Problems// section can now be filtered by one or several individually selected severities. Previously, there was only filtering by minimum severity level available.