Zabbix Documentation 5.0

3.04.04.4 (current)| In development:5.0 (devel)| Unsupported:1.82.02.22.43.23.44.2Guidelines

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
Next revision
Previous revision
manual:introduction:whatsnew500 [2020/01/27 14:05]
marinagen minimum DB versions change added
manual:introduction:whatsnew500 [2020/03/30 10:56] (current)
martins-v some rewording
Line 3: Line 3:
 <note important>​Zabbix 5.0.0 is not released yet.</​note>​ <note important>​Zabbix 5.0.0 is not released yet.</​note>​
  
 +=== Test item from UI ===
  
-=== Minimum required ​versions for databases updated === +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. 
-The required ​version numbers ​of [[:manual/installation/requirements#Software|databases]] have been renewed.+ 
 +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 === === IPMI sensor discovery ===
Line 14: Line 47:
  
 The maximum allowed length of an item key has been raised from 256 to 2048 characters. The maximum allowed length of an item key has been raised from 256 to 2048 characters.
 +
 +=== Binary64 floating point values ===
 +
 +Binary64 floating point numbers are now supported in new installations. For upgraded installations,​ a [[:​manual/​installation/​upgrade_notes_500#​support_of_binary64_floating_point_values|manual patch]] must be applied for binary64 floating point number support.
 +
 +=== ODBC monitoring without DSN ===
 +A new ''​connection string''​ parameter has been added to ''​db.odbc.*''​ items. Now //​[[:​manual/​config/​items/​itemtypes/​odbc_checks|Database monitor]]// items can be configured in two ways:
 +  * Using the data source name as set in /​etc/​odbc.ini
 +  * Using a connection string ​
 +
 +=== Find and replace preprocessing step ===
 +
 +A new item value [[:​manual/​config/​items/​preprocessing|preprocessing]] option has been added allowing to find and replace a specified string with another:
 +
 +{{:​manual:​introduction:​preprocessing_replace.png?​600|}}
 +
 +This step has two parameters:
 +
 +  * //search string// - the string to search for
 +  * //​replacement//​ - the string to replace the search string with. The replacement string may also be empty effectively allowing to delete the search string when found.
 +
 +=== Nanosecond support by Zabbix sender input file ===
 +
 +A new Zabbix sender option
 +
 +<​code>​
 +-N, --with-ns
 +</​code>​
 +
 +allows to support nanoseconds in a Zabbix sender input file. This option can be only used together with the ''​%%--with-timestamps%%''​ option, e.g.:
 +
 +  zabbix_sender -z 127.0.0.1 --with-timestamps --with-ns -i values.txt
 +
 +This option specifies that each line of the input file contains the following, whitespace-delimited:​ ''<​host>​ <key> <​timestamp>​ <ns> <​value>'',​ e.g.:
 +
 +  Zabbix server"​ trap001 1429533600 748744024 43
 +  Zabbix server"​ trap001 1429533600 748791234 44
 +
 +=== Secure connections to Zabbix database ===
 +
 +It is now possible to configure secure TLS connections to MySQL and PostgreSQL databases from:
 +
 +  * [[:​manual/​appendix/​install/​db_encrypt#​frontend_configuration|Zabbix frontend]]
 +  * [[:​manual/​appendix/​install/​db_encrypt#​zabbix_serverproxy_configuration|Zabbix server or proxy]]
  
 === Restricting agent checks === === Restricting agent checks ===
Line 29: Line 106:
  
 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. 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.
- 
-=== Support of IBM DB2 dropped === 
- 
-The IBM DB2 database is no longer supported by Zabbix. 
  
 === Using HTTP proxy in webhooks === === Using HTTP proxy in webhooks ===
Line 40: Line 113:
 When specifying the proxy value the same functionality as in the item configuration [[:​manual/​config/​items/​itemtypes/​http#​configuration|HTTP proxy]] field is supported. 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 ​===+=== New mass update options ​===
  
-It is now possible to mass unlink templates when using host or template mass update:+It is now possible to
 +  * Mass update user macros defined on a host or template level 
 +  * Mass unlink templates when using host or template mass update:
  
-{{:​manual:​introduction:​hosts_mass_unlink.png|}}+{{:​manual:​introduction:​hosts_mass_unlink1.png|}}
  
 See also: See also:
Line 56: Line 131:
  
 {{:​manual:​introduction:​msg_templates.png?​600|}} {{:​manual:​introduction:​msg_templates.png?​600|}}
 +
 +=== SNMP credentials at host interface level ===
 +
 +SNMP version and credentials in previous versions were set at an item level. In the new version, all of these can be set at a host interface level:
 +
 +{{:​manual:​introduction:​snmp_interface_credentials.png|}}
 +
 +See also: [[:​manual/​config/​items/​itemtypes/​snmp#​configuring_snmp_monitoring|Configuring SNMP monitoring]]
 +
 +When creating an item, the item type dropdown no longer has three entries for SNMP v1, v2 and v3 agent. Instead there is just an //SNMP agent// type and the ability to select the SNMP interface as required.
 +
 +=== Manual SNMP cache clearing ===
 +Zabbix server and Zabbix proxy now support an ''​-R snmp_cache_reload''​ runtime control [[:​manual/​concepts/​server#​running_server|option]],​ which reloads the SNMP cache and clears the SNMP properties (engine time, engine boots, engine id, credentials) for all hosts. Net-SNMP version 5.3.0 or higher is required. ​
 +
 +=== SIGNL4 webhook integration ===
 +
 +SIGNL4 integration is available allowing to use the [[manual/​config/​notifications/​media/​webhook|webhook]] media type for pushing Zabbix notifications to [[https://​git.zabbix.com/​projects/​ZBX/​repos/​zabbix/​browse/​templates/​media/​signl4|SIGNL4]]
 +
 +==== Macros ====
 +
 +=== Ability to mask macro content in the frontend ===
 +
 +Macro value field now has //Secret text// mode. If enabled, it masks the content of a macro with asterisks to protect sensitive information,​ such as passwords or shared keys.
 +
 +=== New macros ===
 +The following macros are now supported:
 +
 +  * {EVENT.DURATION} will return the duration of an event.
 +  * {EVENT.TAGSJSON} and {EVENT.RECOVERY.TAGSJSON} macros will resolve to a JSON array containing event tag [[:​manual/​api/​reference/​event/​object#​event_tag|objects]] or recovery event tag objects.
 +
 +For more details, see [[:​manual/​appendix/​macros/​supported_by_location|Macros supported by location]].
 +
 +
 +=== 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
 +
 +=== TimescaleDB native compression support ===
 +TimescaleDB native compression is now supported in Zabbix server installations with PostgreSQL version 10.2 or higher and TimescaleDB version 1.5 or higher.
 +
 +==== New templates ====
 +New official templates are available for monitoring:
 +
 +=== Server ===
 +  * //Template Server Chassis by IPMI// - server chassis monitoring with BMC over IPMI.
 +  * //Template App Memcached// - Memcached server monitoring via Zabbix agent 2.
 +
 +=== Docker ===
 +  * //Template App Docker// - Docker monitoring via Zabbix agent 2. 
 +
 +You can get these templates:
 +
 +  * In //​Configuration//​ -> //​Templates//​ in new installations;​
 +  * When upgrading from previous versions, the latest templates can be downloaded from the [[https://​git.zabbix.com/​projects/​ZBX/​repos/​zabbix/​browse/​templates|Zabbix Git repository]] and manually imported into Zabbix in the //​Configuration//​ -> //​Templates//​ section. If a template with the same name already exists, check the //Delete missing// option before importing to achieve a clean import. This way the items that have been excluded from the updated template will be removed (note, that history of the deleted items will be lost).
  
 ==== Frontend ==== ==== 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 === === Page selection dropdown integrated into headings ===
Line 77: Line 229:
   * //​Administration//​ -> //General//   * //​Administration//​ -> //General//
   * //​Administration//​ -> //Queue//   * //​Administration//​ -> //Queue//
 +
 +=== New section for monitoring all hosts ===
 +The new frontend section //​Monitoring -> Hosts// provides detailed view of all monitored devices in a single location. To simplify the navigation //Web// and //Graphs// sections have been removed from the top menu in //​Monitoring//​. Both sections can now be accessed by clicking on respected links in //​Monitoring -> Hosts// section. ​
 +
 +The following information is available from //​Monitoring -> Hosts//: ​
 +  * Hostname ​
 +  * Main interface ​
 +  * Availability ​
 +  * Tags 
 +  * Problems (icons indicating currently open problems)
 +  * Status ​
 +  * Latest data (link to //Latest data// section) ​
 +  * Problems (link to //​Problems//​ section) ​
 +  * Graphs (number of graphs and a link to //Graphs// section) ​
 +  * Screens (number of screens and a link to //Screens// section) ​
 +  * Web scenarios (number of web scenarios and a link to //Web// section)
 +Links in the list above provide a convenient way to view corresponding page with more details about the given host. Users with admin and superadmin rights can also quickly navigate to the host's configuration page from the section. See [[:​manual/​web_interface/​frontend_sections/​monitoring/​hosts|this page]] for more details. ​
 +
 +{{:​manual:​introduction:​monitoring_hosts_wn.png?​600|}}
 +
 === Detail editing as popup window === === Detail editing as popup window ===
  
Line 83: Line 255:
   * Action conditions   * Action conditions
   * Global correlation conditions   * Global correlation conditions
 +  * Problem update screen
   * Action operation details ​   * 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     * 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
Line 94: Line 267:
 {{:​manual:​introduction:​oper_details_new.png?​600|}} {{:​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. 
 +=== Ability to download graph widgets as images ===
 +Screenshots of [[:​manual/​web_interface/​frontend_sections/​monitoring/​dashboard/​widgets#​graph|Graph]] widget and [[manual/​web_interface/​frontend_sections/​monitoring/​dashboard/​widgets#​graph_classic|Graph (classic)]] widget can now be downloaded as .png files from the widget context menu.
 +=== 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.
 +
 +=== Miscellaneous ===
 +
 +  * The latest data page no longer displays nothing when opened for the first time. 
 +  * The list of web scenario HTTP user agents has been updated.
 +
 +==== Daemons ====
 +
 +=== Remote command logging on agent ===
 +
 +Remote command logging, if enabled on Zabbix [[:​manual/​appendix/​config/​zabbix_agentd|agent]]/​[[:​manual/​appendix/​config/​zabbix_agent2|agent2]] (LogRemoteCommands=1) will no longer create log entries for system.run[] if it is launched locally by HostMetadataItem,​ HostInterfaceItem or HostnameItem parameters. system.run[] commands will be logged only if executed remotely.
 +
 +=== Crypto libraries ===
 +
 +Support of the mbedTLS (PolarSSL) crypto library has been discontinued.
 +
 +=== JMX monitoring attributes with tabular data ===
  
 +Support of [[:​manual/​config/​items/​itemtypes/​jmx_monitoring#​attributes_returning_tabular_data|tabular data]] objects in JMX Mbean attributes has been added. It is supported for the JMX agent data collection and low-level discovery.