30 Questions
In the Zabbix JSON format, where are macro names already defined?
In the LLD rule properties (LLD macros tab)
What is a mandatory requirement for item prototypes in Low-level Discovery (LLD)?
Unique keys
What does the 'Create enabled' attribute do for item/trigger prototypes?
Determines if the item/trigger will be added in an enabled state
Where should LLD {#MACRO} be used for item prototypes?
As the key's parameter
What is the purpose of trigger prototype dependencies in LLD?
To establish relationships between trigger prototypes and regular triggers
What is the purpose of replacing tabs with semicolons in preprocessing?
To prepare raw data for JSON conversion
Where can LLD {#MACRO} be used in trigger prototypes?
In the trigger name
What are the additional attributes of item/trigger prototypes?
Description, Create enabled, Discover
What is the purpose of mapping LLD macros to JSON path in the Zabbix JSON format?
To define the location of LLD macros in the JSON data block
What is the role of the built-in CSV to JSON functionality in Low-level Discovery?
To convert raw data separated by tabs into JSON format
What are the entity prototypes of a Low-Level Discovery (LLD) rule?
Item prototypes, Trigger prototypes, Graph prototypes, Host prototypes
What is recommended for a Low-Level Discovery (LLD) rule's name and unique key?
Both should include the word 'discovery'
What happens if a prototype is changed in a Low-Level Discovery (LLD) rule?
The entities will be updated upon the next execution of the discovery rule
What can be used to force the update of entities in a Low-Level Discovery (LLD) rule for passive checks?
Execute now
What must a Low-Level Discovery (LLD) rule have in terms of properties?
A name and a unique key
What are the components of an LLD rule?
Item prototypes, Trigger prototypes, Graph prototypes, Host prototypes
What is the purpose of entity prototypes in a Low-Level Discovery (LLD) rule?
They serve as blueprints for the entities
What is the similarity between Low-Level Discovery (LLD) rule properties and regular Zabbix item properties?
Both must have a name and a unique key
What is the action to manually force the update of entities in a Low-Level Discovery (LLD) rule for passive checks?
Execute now
What is the purpose of LLD rule properties?
To define the characteristics and behavior of the LLD rule
What is the impact of a too frequent execution of LLD rule on proxies sending LLD data to Zabbix server?
It can potentially degrade proxy performance
What happens when an LLD rule is disabled?
New entities are not created, lost entities are not removed, and changes to prototypes have no effect on existing items and triggers
What is the default period for keeping lost entities?
30 days
What is the maximum period for keeping lost entities?
25 years
What is the purpose of LLD macros in low-level discovery rules?
Used for creating prototypes and returning real values of various components
What do built-in discovery items have predefined LLD macros for?
Various components such as mounted filesystems, block devices, network interfaces, CPU, Windows services, and systemd services
What type of data blocks do discovery rules rely on to generate LLD macros?
JSON data blocks
What formats are supported by Zabbix for generating LLD macros?
Zabbix JSON format or custom JSON format
What is involved in a practical setup for low-level discovery rules?
Creating a new template, setting up a discovery rule, creating item prototypes, and linking the template to a specific host for manual execution and result checking
What processes are involved in low-level discovery?
Data collection, optional preprocessing of data in JSON format, and passing data to a free LLD worker process
Study Notes
Zabbix Low-Level Discovery (LLD) Internals
- LLD update interval determines how often the LLD rule is executed, impacting the creation, removal, or updating of entities based on received discovery data.
- Proxies sending LLD data to Zabbix server can potentially degrade proxy performance if execution is too frequent.
- Low-level discovery involves multiple processes: data collection, optional preprocessing of data in JSON format, and passing data to a free LLD worker process.
- Multiple LLD workers can be started on the Zabbix server if needed, with the option to define the number of pre-forked instances of low-level discovery processors.
- Item prototypes are created under LLD rules, and all entities created by LLD display the rule name in orange color.
- Lost entities are kept for a default period of 30 days, with a maximum period of 25 years, and can be automatically removed after this period.
- Disabling an LLD rule results in new entities not being created, lost entities not being removed, and changes to prototypes having no effect on existing items and triggers.
- Deleting a prototype immediately deletes every entity created from it, and deleting a discovery rule leads to the immediate deletion of all entities created by the rule.
- Practical setup involves creating a new template, setting up a discovery rule, creating item prototypes, and linking the template to a specific host for manual execution and result checking.
- Low-level discovery rules return data in LLD macros, which are used for creating prototypes and return real values of file system names, network interfaces, SNMP OIDs, etc.
- Built-in discovery items have predefined LLD macros for various components such as mounted filesystems, block devices, network interfaces, CPU, Windows services, and systemd services.
- Discovery rules rely on JSON data blocks to generate LLD macros, and Zabbix supports the use of Zabbix JSON format or custom JSON format for this purpose, with older agent discovery data formats also being supported.
Test your knowledge of Zabbix Low-Level Discovery (LLD) internals with this quiz. Explore key concepts such as LLD update intervals, entity creation, item prototypes, LLD macros, and practical setup steps.
Make Your Own Quizzes and Flashcards
Convert your notes into interactive study material.
Get started for free
