This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
manual:introduction:whatsnew540 [2021/01/14 06:39] marinagen [ZBXNEXT-5518] XML to JSON |
manual:introduction:whatsnew540 [2021/02/26 13:18] (current) martins-v adding 'unique short description' jmx item parameter (ZBXNEXT-735) |
||
---|---|---|---|
Line 3: | Line 3: | ||
<note important> Zabbix 5.4.0 is not released yet.</note> | <note important> Zabbix 5.4.0 is not released yet.</note> | ||
- | ==== Naming in JavaScript objects ==== | + | ==== JavaScript global scripts ==== |
+ | [[:manual/web_interface/frontend_sections/administration/scripts|Global scripts]] now support custom logic written in JavaScript with the ability to call external HTTP services. | ||
+ | |||
+ | To configure JavaScript code as global script, select the new Webhook script type: | ||
+ | |||
+ | {{:manual:introduction:script_webhook.png|}} | ||
+ | |||
+ | The Webhook script type offers three fields for adding the parameters, the JavaScript code and timeout. | ||
+ | |||
+ | Additionally, all defined global scripts now can be executed from the [[:manual/web_interface/frontend_sections/monitoring/problems#event_menu|event menu]]. | ||
+ | |||
+ | ==== Host availability on interface level ==== | ||
+ | |||
+ | All data about host availability have been moved from the host level to the level of individual interfaces. If a host has several interfaces of the same type and one interface becomes unavailable, it does not affect the availability of any other interface of the same type. | ||
+ | |||
+ | The way that host availability is displayed has been changed: | ||
+ | |||
+ | * Availability icons in the frontend are now only displayed for those interfaces (Zabbix agent, SNMP, IPMI, JMX) that have been configured on the host | ||
+ | * If you position the mouse over the availability icon, a popup list of all interfaces of this type appears with each interface details, status and errors | ||
+ | * Yellow has been added as a new status color for the availability icon | ||
+ | * The meaning of the availability icon colors has been updated as follows: | ||
+ | * //green// - all interfaces of this type are available | ||
+ | * //yellow// - at least one interface of this type available and at least one unavailable; others can have any value including 'unknown' | ||
+ | * //red// - no interfaces of this type available | ||
+ | * //gray// - at least one interface of this type unknown (none unavailable) | ||
+ | * The ''zabbix[host,<type>,available]'' internal item now reports availability of the main interface of a particular type of checks | ||
+ | * The logic of counting host availability has also been updated in the //Host availability// dashboard widget (see [[:manual/web_interface/frontend_sections/monitoring/dashboard/widgets#host_availability|details]]) | ||
+ | |||
+ | ==== API tokens ==== | ||
+ | |||
+ | Support of API authorization tokens has been added. Now it is possible to access Zabbix API using either a token or a Zabbix username and password for authorization. An opportunity to allow/deny management of API tokens has been added to user role permissions. Super admins with sufficient permissions can create and manage API tokens in the //Administration->General// [[:manual/web_interface/frontend_sections/administration/general#api_tokens|frontend section]] or via the new ''token.*'' [[:manual/api/reference/token|API methods]]. Other users with permission to manage API tokens can view tokens assigned to them in [[:manual/web_interface/user_profile|user settings]] or via API. | ||
+ | |||
+ | ==== JavaScript objects ==== | ||
+ | |||
+ | === Naming === | ||
The 'CurlHttpRequest' object has been renamed to 'HttpRequest' for simplicity. The previous object naming is now deprecated and its support will be discontinued after Zabbix 6.0. | The 'CurlHttpRequest' object has been renamed to 'HttpRequest' for simplicity. The previous object naming is now deprecated and its support will be discontinued after Zabbix 6.0. | ||
Line 18: | Line 52: | ||
|post |Post | | |post |Post | | ||
|delete |Delete | | |delete |Delete | | ||
+ | |setHttpAuth |SetHttpAuth | | ||
|setProxy |SetProxy | | |setProxy |SetProxy | | ||
|getStatus |Status | | |getStatus |Status | | ||
Line 30: | Line 65: | ||
|console.error(object) |Zabbix.log(2, JSON.stringify(object)) | | |console.error(object) |Zabbix.log(2, JSON.stringify(object)) | | ||
- | See also: [[:manual/config/items/preprocessing/javascript/javascript_objects|Additional JavaScript objects]] | + | === XML object === |
- | ==== XML parsing in JavaScript ==== | + | New JavaScript object //XML// has been added to provide an ability to extract data by XPath and convert XML to JavaScript object (JSON) and vice versa. |
- | New [[:manual/config/items/preprocessing|preprocessing]] option //XML to JSON// has been added to provide an ability to extract data by XPath and convert XML to JavaScript and vice versa. | + | |
+ | See also: [[:manual/config/items/preprocessing/javascript/javascript_objects|Additional JavaScript objects]]. | ||
+ | |||
+ | ==== XML to JSON preprocessing option ==== | ||
+ | |||
+ | New option //XML to JSON// has been added in [[:manual/config/items/preprocessing|item preprocessing]] and [[:manual/discovery/low_level_discovery#preprocessing|low-level discovery preprocessing]]. | ||
+ | |||
+ | ==== Strong encryption protocols for SNMPv3 ==== | ||
+ | |||
+ | Support of strong authentication and privacy protocols for SNMPv3 has been implemented. | ||
+ | |||
+ | For authentication: | ||
+ | |||
+ | * SHA224 | ||
+ | * SHA256 | ||
+ | * SHA384 | ||
+ | * SHA512 | ||
+ | |||
+ | For privacy: | ||
+ | |||
+ | * AES192 | ||
+ | * AES256 | ||
+ | * AES192C (Cisco) | ||
+ | * AES256C (Cisco) | ||
+ | |||
+ | Also, after the upgrade the existing SHA and AES protocols will be renamed to SHA1 and AES128 respectively. | ||
+ | |||
+ | See also: [[:manual/config/items/itemtypes/snmp#step_2|Configuring SNMP hosts]] | ||
==== Trend function cache ==== | ==== Trend function cache ==== | ||
Line 62: | Line 124: | ||
In low-level discovery, it is now possible to set up filtering by the specified macro presence (or absence). Two new [[:manual/discovery/low_level_discovery#filter|filter]] condition operators have been added: "exists" and "does not exist". | In low-level discovery, it is now possible to set up filtering by the specified macro presence (or absence). Two new [[:manual/discovery/low_level_discovery#filter|filter]] condition operators have been added: "exists" and "does not exist". | ||
+ | |||
+ | ==== Oracle database setup === | ||
+ | |||
+ | * When [[:manual/appendix/install/oracle#database_creation|creating]] an Oracle database, it is no longer required to copy images to the Oracle host. | ||
+ | * Support of Net Service Name connection method has been added. Now Zabbix supports two types of connect identifiers (connection methods): Easy Connect and Net Service Name. See [[:manual/appendix/install/oracle#connection_set_up|Oracle database setup]]for more information. | ||
==== Items ==== | ==== Items ==== | ||
Line 68: | Line 135: | ||
A new ''vmware.cl.perfcounter[<url>,<id>,<path>,<instance>]'' [[:manual/config/items/itemtypes/simple_checks/vmware_keys|item]] allows to retrieve VMware cluster performance counter metrics. | A new ''vmware.cl.perfcounter[<url>,<id>,<path>,<instance>]'' [[:manual/config/items/itemtypes/simple_checks/vmware_keys|item]] allows to retrieve VMware cluster performance counter metrics. | ||
+ | |||
+ | === JMX items === | ||
+ | |||
+ | JMX monitoring and discovery items ''jmx[]'', ''jmx.discovery[]'' and ''jmx.get[]'' have a new third parameter - 'unique short description', allowing to use multiple instances of the same check on the host. | ||
+ | |||
+ | See also: | ||
+ | * [[:manual/config/items/itemtypes/jmx_monitoring#adding_jmx_agent_item|Adding JMX items]] | ||
+ | * [[:manual/discovery/low_level_discovery/examples/jmx#item_key|JMX object discovery]] | ||
==== Macros ==== | ==== Macros ==== | ||
Line 73: | Line 148: | ||
* A new {ITEM.VALUETYPE} [[:manual/appendix/macros/supported_by_location|macro]] has been added returning the value type of the item. Possible values: 0 - numeric float, 1 - character, 2 - log, 3 - numeric unsigned, 4 - text. | * A new {ITEM.VALUETYPE} [[:manual/appendix/macros/supported_by_location|macro]] has been added returning the value type of the item. Possible values: 0 - numeric float, 1 - character, 2 - log, 3 - numeric unsigned, 4 - text. | ||
* Time period handling of the **fmttime** [[:manual/config/macros/macro_functions|macro function]] has become more flexible. | * Time period handling of the **fmttime** [[:manual/config/macros/macro_functions|macro function]] has become more flexible. | ||
+ | |||
+ | ==== New templates ==== | ||
+ | |||
+ | The following templates are now available for out-of-the-box monitoring: | ||
+ | |||
+ | * //Hikvision camera by HTTP// - see [[:manual/config/templates_out_of_the_box/http|setup instructions]] for HTTP templates. | ||
+ | |||
+ | You can get these templates: | ||
+ | |||
+ | * In //Configuration// -> //Templates// in new installations; | ||
+ | * If you are upgrading from previous versions, you can download these templates from Zabbix [[https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates|Git repository]] or find them in the ''templates'' directory of the downloaded latest Zabbix version. Then, while in //Configuration// -> //Templates// you can import them manually into Zabbix. | ||
==== Frontend ==== | ==== Frontend ==== | ||
+ | === Value mapping on template/host level === | ||
+ | |||
+ | Value mapping is now configured on template/host level, in the [[:manual/config/templates/template|template]] and [[:manual/config/hosts/host|host]] configuration forms respectively. Global value mapping has been removed. | ||
+ | |||
+ | Additionally: | ||
+ | |||
+ | * the field in item configuration for selecting a value map has been renamed from //Show value// to //Value mapping// | ||
+ | * the item list can be searched for the value map used | ||
+ | |||
+ | See also: [[:manual/config/items/mapping|Value mapping]] | ||
+ | |||
+ | === Negated filtering by tags === | ||
+ | |||
+ | In several frontend filters it is now possible to filter entities: | ||
+ | |||
+ | * by tag name only | ||
+ | * based on tags **not** having the specified name or value | ||
+ | |||
+ | This is implemented by adding new operators "Exists", "Does not exist", "Does not equal" and "Does not contain" in the tag filter conditions. | ||
+ | |||
+ | {{:manual:introduction:tag_conditions.png|}} | ||
+ | |||
+ | These filtering changes are implemented in: | ||
+ | |||
+ | * Monitoring: | ||
+ | * Problem-related dashboard widgets (//Graph//, //Problem hosts//, //Problems//, //Problems by severity//) | ||
+ | * Problems | ||
+ | * Hosts | ||
+ | * Configuration: | ||
+ | * Templates | ||
+ | * Hosts | ||
+ | * Triggers | ||
=== Unified global event correlation form === | === Unified global event correlation form === | ||
Line 85: | Line 203: | ||
For template entities: | For template entities: | ||
- | * the //Host// column and //Hosts// filter field are renamed to //Template// and //Templates// respectedly; | + | * the //Host// column and //Hosts// filter field are renamed to //Template// and //Templates// respectively; |
* the //Info// column is no longer displayed; | * the //Info// column is no longer displayed; | ||
* filters have been updated to offer only options that are relevant to templates (State, Discovery, and some other selectors have been removed); | * filters have been updated to offer only options that are relevant to templates (State, Discovery, and some other selectors have been removed); | ||
Line 92: | Line 210: | ||
For host entities, some drop-down filter selectors have been replaced with buttons, not affecting the functionality; //Host group// selector now allows selecting only host groups that contain at least one host; //Hosts// selector now allows selecting hosts only. | For host entities, some drop-down filter selectors have been replaced with buttons, not affecting the functionality; //Host group// selector now allows selecting only host groups that contain at least one host; //Hosts// selector now allows selecting hosts only. | ||
+ | |||
+ | === Third-level menu === | ||
+ | Some sections of the main menu in Zabbix now have an additional menu level that appears upon a mouse-click. A small right arrow next to the section name indicates that this section has a third-level menu. This change affects only sections that contain multiple pages: | ||
+ | |||
+ | * //Monitoring// -> //Overview// | ||
+ | * //Monitoring// -> //Screens// | ||
+ | * //Configuration// -> //Actions// | ||
+ | * //Administration// -> //General// | ||
+ | * //Administration// -> //Queue// | ||
+ | |||
+ | The third-level menu is introduced as a more visible alternative to the title dropdown on the top of a page. The title dropdown is also still available, therefore users can select any of the two options for navigating between pages. | ||
+ | |||
+ | |{{actions_menu.png?300|}} |{{actions_selector.png?300|}} | | ||
+ | |Third-level menu. |Title dropdown. | | ||
=== Hidden PSK data for hosts and proxies === | === Hidden PSK data for hosts and proxies === |