order to support preprocessing of low-level discovery result and custom paths to low-level discovery (LLD) macro values in a JSON document, the format of JSON returned by low-level discovery rules has been normal JSON containing an array. Built-in discovery keys have been updated to return an array of LLD rows at the root of JSON document. Zabbix will automatically extract a macro and value if an array item Low-level discovery rule now can also be a dependent item, depending on a regular item. Low-level discovery rule cannot be dependent on another low-level discovery rule. To configure it as a dependent

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 Web scenarios Overriding in LLD rules It is now possible to filter out items, triggers, hosts and graphs or override their attributes during low-level discovery based on LLD object and prototype name value the same functionality as in the item configuration HTTP proxy field is supported. Discovery rule filtering The list of low-level discovery rules previously was always linked to a single host, making

unsupported, now it is possible to use a new preprocessing rule called ”Check for not supported value” to handle this situation. This preprocessing rule has standard Custom on fail options allowing to: • discard created: • Inherit (default) - the hosts will be created with the interface of a host the Discovery rule belongs to. If a host prototype is configured on the template level, then discovered hosts will inherit will be created without interfaces. Tags Additionally, support of tags with a possibility to use LLD macros as tag values has been added to the host prototypes. This functionality allows assigning each

the returned JSON, however, these macros can be defined by the user as required, using the custom LLD macro functionality with JSONPath to point to the required values in the returned JSON. Low-level low-level discovery macros and therefore can return values without the limitations associated with LLD macro name generation (for example, hyphens, square brackets and non-ASCII characters): jmx.get[ characters not supported in LLD macro name generation), had to ignore these properties. The new jmx.get[] item does not generate LLD macro names in the returned JSON. Instead, LLD macro names may be defined

the reason why an item, an LLD-rule, or a trigger became unsupported: • {ITEM.STATE.ERROR} - for item-based internal notifications; • {LLDRULE.STATE.ERROR} - for LLD-rule based internal notifications; macros in item name no longer supported The support for user macros in item names (including discovery rule names), deprecated since Zabbix 4.0, has been fully removed. Databases To create the optimal user configuration changes for all Zabbix objects, including changes that occurred as a result of executing an LLD rule, a network discovery action, an autoregistration action, or a script execution. Previously, configuration

previous versions the same functionality was available in the Configuration section (item/discovery rule form and lists) only. As another improvement, it is now also possible to ”Execute now” dependent implemented to simplify further processing of the returned JSON (for example, in preprocessing steps or LLD macros). Tag reading from VMware VMware items reporting various VMware tags (e.g., vmware.datastore entities on a particular device (e.g. file systems, network interfaces, etc). low-level discovery rule - set of definitions for automated discovery of low-level entities on a device. item prototype

0 5.1 Defining multiple filters for low level discovery The filter section in low level discovery rule definition has been split out into a separate tab and, most importantly, allows to define several is based on custom graph prototypes created in low-level discovery (LLD) rules. 12 In monitoring, the screen cell will display an LLD-generated graph as soon as it is generated. If the graph is not generated prototypes in low-level discovery. In monitoring, the screen cell will display a graph created from an LLD-generated item. If the item is not generated, nothing will be displayed. The functionality is supported

events • ”Event type” conditions for internal events - Item in “normal” state, Low-level discovery rule in “normal” state, Trigger in “normal” state 11 For more details, see: • Actions • Recovery operations also: • Upgrade notes for 3.2 • Action operations 5.11 Viewable items, triggers, graphs created by LLD Entities created by low-level discovery (items, triggers, graphs) in previous Zabbix versions were be displayed by default. Processing low-level discovery (LLD) LLD rule processing has been modified so multiple values for the same LLD rule are not processed simultaneously. For more details, see the