Zabbix Documentation 4.2

2.23.04.04.2 (current)In development:4.4 (devel)Unsupported:1.82.02.43.23.4

User Tools

Site Tools


manual:discovery:low_level_discovery

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:discovery:low_level_discovery [2019/03/28 13:43]
martins-v adding 'prometheus to json' preprocessing
manual:discovery:low_level_discovery [2019/07/01 06:36] (current)
martins-v fixing typo
Line 87: Line 87:
 |   ​|//​Discard unchanged with heartbeat// ​ |Discard a value if it has not changed within the defined time period (in seconds).\\ Positive integer values are supported to specify the seconds (minimum - 1 second). Time suffixes can be used in this field (e.g. 30s, 1m, 2h, 1d). User macros and low-level discovery macros can be used in this field.\\ Only one throttling option can be specified for a discovery item.\\ E.g. ''​1m''​. If identical text is passed into this rule twice within 60 seconds, it will be discarded.\\ //Note//: Changing item prototypes does not reset throttling. Throttling is reset only when preprocessing steps are changed. ​ | |   ​|//​Discard unchanged with heartbeat// ​ |Discard a value if it has not changed within the defined time period (in seconds).\\ Positive integer values are supported to specify the seconds (minimum - 1 second). Time suffixes can be used in this field (e.g. 30s, 1m, 2h, 1d). User macros and low-level discovery macros can be used in this field.\\ Only one throttling option can be specified for a discovery item.\\ E.g. ''​1m''​. If identical text is passed into this rule twice within 60 seconds, it will be discarded.\\ //Note//: Changing item prototypes does not reset throttling. Throttling is reset only when preprocessing steps are changed. ​ |
 ^Prometheus ​ ^^^ ^Prometheus ​ ^^^
-|:::|//​Prometheus to JSON// ​ |Convert required Prometheus metrics to JSON.\\ See [[:​manual/​config/​items/​itemtypes/​prometheus|Prometheus checks]] for more details. ​ |+  ​|//​Prometheus to JSON// ​ |Convert required Prometheus metrics to JSON.\\ See [[:​manual/​config/​items/​itemtypes/​prometheus|Prometheus checks]] for more details. ​ |
  
 Note that if the discovery rule has been applied to the host via template then the content of this tab is read-only. Note that if the discovery rule has been applied to the host via template then the content of this tab is read-only.
Line 94: Line 94:
 == Custom macros == == Custom macros ==
  
-The **LLD macros** tab allows specify low-level discovery macro mappings with a custom JSONPath, allowing to extract discovery macro values to use in discovered items, triggers, etc. Note that this action will be applied to the result of discovery and the preprocessing applied so far (see above).+The **LLD macros** tab allows ​to specify low-level discovery macro mappings with a custom JSONPath, allowing to extract discovery macro values to use in discovered items, triggers, etc. Note that this action will be applied to the result of discovery and the preprocessing applied so far (see above).
  
 {{manual:​discovery:​low_level_discovery:​lld_rule_fs0c.png|}} {{manual:​discovery:​low_level_discovery:​lld_rule_fs0c.png|}}
Line 187: Line 187:
 {{manual:​discovery:​low_level_discovery:​discovered_items1.png|}} {{manual:​discovery:​low_level_discovery:​discovered_items1.png|}}
  
-Note that discovered entities will not be created in case there are already existing entities with the same uniqueness criteria, for example, an item with the same key or graph with the same name. An error message is displayed in this case that the low-level discovery rule could not create certain entities.+Note that discovered entities will not be created in case there are already existing entities with the same uniqueness criteria, for example, an item with the same key or graph with the same name. An error message is displayed in this case in the frontend ​that the low-level discovery rule could not create certain ​entities. The discovery rule itself, however, will not turn unsupported because some entity could not be created and had to be skipped. The discovery rule will go on creating/​updating other entities.
  
 Items (similarly, triggers and graphs) created by a low-level discovery rule will be deleted automatically if a discovered entity (file system, interface, etc) stops being discovered (or does not pass the filter anymore). In this case the items, triggers and graphs will be deleted after the days defined in the //Keep lost resources period// field pass. Items (similarly, triggers and graphs) created by a low-level discovery rule will be deleted automatically if a discovered entity (file system, interface, etc) stops being discovered (or does not pass the filter anymore). In this case the items, triggers and graphs will be deleted after the days defined in the //Keep lost resources period// field pass.