manual:introduction:whatsnew600

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:whatsnew600 [2017/09/13 06:24]
manual:introduction:whatsnew600 [2021/09/14 13:33]
marinagen [ZBXNEXT-6870] new HTTP methods supported
Line 1: Line 1:
 +===== 5 What's new in Zabbix 6.0.0 =====
 +
 +<note important>​ Zabbix 6.0.0 is not released yet.</​note>​
 +
 +==== Services ====
 +
 +Several updates have been made in the new version to the high-level overview of the monitored infrastructure offered by the services functionality.
 +
 +=== Tag-based mapping of services to problems ===
 +
 +The availability of [[:​manual/​web_interface/​frontend_sections/​monitoring/​it_services|services]] in previous Zabbix versions depended on triggers and their states. In the new version that is replaced by a tag-based mapping to problems for the respective service.
 +
 +The configuring and viewing of services is now merged in //​Monitoring//​ -> //​Services//,​ and a separate section for service configuration no longer exists in //​Configuration//​ -> //​Services//​.
 +
 +In service configuration,​ hard and soft dependencies no longer exist. Instead, a service can have multiple parent services. ​
 +
 +=== Status ​calculation ​and propagation rules ===
 +
 +There are new status calculation rules and flexible ​additional rules for calculating the status of a parent service based on the statuses and weight of direct children. It is now also possible to set flexible rules for propagating a service status to parent services.
 +
 +=== Permissions to services ===
 +
 +Flexible permissions to services have been implemented on [[:​manual/​web_interface/​frontend_sections/​administration/​user_roles|user role]] level. Read-write or read-only access can be granted to none, all or selected services (based on name or tags).
 +
 +=== Alerting on service status change ===
 +
 +It is now possible to receive automated alerts about service status changes, similar to the alerts about trigger status changes. ​
 +
 +A new [[manual/​config/​notifications/​action|service action]] type has been added to the //Actions// menu. Service actions may include steps for problem, recovery, and update operations related to services. It is possible to configure two types of actions: sending a message to the specified recipients and executing a remote command on Zabbix server. Similarly to trigger actions, service actions support problem [[manual/​config/​notifications/​action/​escalations|escalation]] scenarios. ​
 +
 +New message templates //​Service//,​ //Service recovery//, and //Service update// have been added to [[manual/​config/​notifications/​media#​common_parameters|media types]] and should be defined to enable correct sending of notifications for service actions. ​
 +
 +==== Simple macros replaced by expression macros ====
 +
 +A new expression syntax for triggers and calculated items was introduced in [[https://​www.zabbix.com/​documentation/​5.4/​manual/​introduction/​whatsnew540|Zabbix 5.4]]. However, the old syntax still remained in use in simple macros. In the new version, the functionality of simple macros has been transferred to expression macros and the new expression syntax is used. See the comparison below for details of the change:
 +
 +^In Zabbix 6.0^Before Zabbix 6.0^
 +|''​%%{?​avg(/​host/​key,​1h)}%%''​\\ \\ Example of an expression macro in the new version. ​ |''​%%{host:​key.avg(1h)}%%''​\\ \\ Example of a simple macro in previous versions. ​ |
 +
 +The existing simple macros will be converted to expression macros during the upgrade. The scope of expression macros covers the same that was offered by simple macros. Thus, expression macros can be used in:
 +
 +  * problem notifications and commands
 +  * problem update notifications and commands
 +  * map element labels
 +  * map link labels
 +  * map shape labels
 +  * graph names
 +==== Functions ====
 +
 +=== Monotonic change ===
 +
 +It is now possible to check for monotonic increase or decrease in item values using the new **monoinc()** or **monodec()** [[:​manual/​appendix/​functions/​history|history functions]].
 +
 +=== Number of entities ===
 +New [[manual/​appendix/​functions|functions]] have been added to simplify counting of specific hosts, items, or values, returned by [[:​manual/​appendix/​functions/​aggregate/​foreach|foreach functions]].
 +
 +Aggregate functions: ​
 +  * **count** - total number of values in an array returned by a foreach function (returns an integer); ​
 +  * **item_count** - total number of currently enabled items that match filter criteria (returns an integer).
 +
 +Foreach function:
 +  * **exists_foreach** - number of currently enabled items that match filter criteria (returns an array).
 +
 +==== Items ====
 +
 +Several new items have been added to Zabbix agent/agent 2:
 +
 +  * **agent.hostmetadata** - return host metadata
 +  * **kernel.openfiles** - return the number of open file descriptors
 +  * **net.tcp.socket.count[]** - return the number of TCP sockets that match parameters
 +  * **net.udp.socket.count[]** - return the number of UDP sockets that match parameters
 +  * **vfs.file.get[]** - return information about a file as JSON
 +  * **vfs.file.owner[]** - return the ownership of a file
 +  * **vfs.file.permissions[]** - return a 4-digit string containing octal number with Unix permissions
 +
 +Additionally: ​
 +  * **vfs.file.cksum[]** now supports a second ''​mode''​ parameter (//crc32//, //md5//, //sha256//)
 +  * **vfs.file.size[]** now supports a second ''​mode''​ parameter (//bytes// or //lines//)
 +  * **vfs.fs.discovery** and **vfs.fs.get** now return an %%{#​FSLABEL}%% macro on Windows (with volume names)
 +
 +For more details see [[:​manual/​config/​items/​itemtypes/​zabbix_agent|agent items]].
 +
 +==== Password requirements ====
 +
 +Custom password complexity requirements can now be provided for Zabbix internal [[manual/​web_interface/​frontend_sections/​administration/​authentication#​internal_authentication|authentication method]]. To prevent Zabbix users from setting weak passwords, it is possible to enforce the following restrictions:​
 +  * Set the minimum password length. ​
 +  * Require a password to contain a combination of uppercase and lowercase letters, digits, and/or special characters.
 +  * Prohibit usage of most common and easily guessable passwords.
 +
 +==== Zabbix get and Zabbix sender timeout ====
 +
 +Zabbix get and Zabbix sender utilities now support a ''​-t <​seconds>''​ or ''​%%--%%timeout <​seconds>''​ timeout parameter. The valid range is:
 +
 +  * 1-30 seconds for Zabbix get (default: 30 seconds)
 +  * 1-300 seconds for Zabbix sender (default: 60 seconds)
 +
 +==== Prometheus queries ====
 +Zabbix Prometheus preprocessing [[manual/​config/​items/​itemtypes/​prometheus|query language]] now supports two additional label matching operators: ​
 +  * **!=** -- select labels that are not equal to the provided string;
 +  * **!~** -- select labels that do not regex-match the provided string.
 +
 +==== Javascript methods ====
 +
 +HTTP methods PATCH, HEAD, OPTIONS, TRACE, CONNECT have been added to the JavaScript engine. Also, the engine now allows sending custom HTTP method requests with the new JS method HttpRequest.customRequest.
 +
 +See also: [[:​manual/​config/​items/​preprocessing/​javascript/​javascript_objects|Additional JavaScript objects]].
 +
 +
 +==== Audit log ====
 +
 +== Improved record display ==
 +[[manual/​web_interface/​frontend_sections/​reports/​audit|Audit log]] now supports filtering records by frontend operation that caused these entries. If several log records have been created as a result of a single operation, for example, linking/​unlinking a template, such records will have the same //Recordset ID//. 
 +
 +== Audit settings ==
 +New [[manual/​web_interface/​frontend_sections/​administration/​general#​audit_log|section]] //Audit log// has been added to the //​Administration->​General//​ menu allowing to enable or disable audit logging. Housekeeping settings for audit, previously located under the //​Housekeeper//​ section, have also been moved to the new //Audit log// section. ​
 +
 +==== Frontend languages ====
 +The default language of Zabbix web interface has been changed from British to American English. Support of British English has been dropped. ​
 +
 +===== Breaking changes =====
 +=== Audit log ===
 +Audit log functionality has been reworked significantly. ​ The updated Audit log contains records of all configuration changes of Zabbix objects and has an improved filter, which allows to view records grouped by frontend operation. Logging can be switched on or off in the //​Administration->​General//​ menu section. ​
 +In order to implement these changes, the previously existing database structure had to be reworked. During an upgrade DB tables ''​auditlog''​ and ''​auditlog_details''​ will be replaced by the new table ''​auditlog''​ with a different format. **Existing audit log records will be deleted.**  ​
 +
 +
 +
 +
 +