-
New Feature Request
-
Resolution: Fixed
-
Minor
-
5.0.4, 5.2.0beta2
-
Sprint 70 (Nov 2020), Sprint 71 (Dec 2020), Sprint 72 (Jan 2021)
-
3
Currently, there is a limitation of LLD rule filtering that doesn't allow to process objects with LLD macro missing.
For example, according to the documentation (SNMP discovery):
If an entity does not have the specified OID, then the corresponding macro will be omitted for this entity.
At this point, having a filter like "{#MACRO} doesn't match VALUE" will fail to execute with the following error:
Cannot accurately apply filter: no value received for macro "{#MACRO}"
At this point, it seems that having something like "{#MACRO} exist" / "{#MACRO} doesn't exist" as an option for the LLD rule filter is a solution.
- is duplicated by
-
ZBXNEXT-5466 Allow for "Custom on fail" also on LLD macros
- Closed
-
ZBXNEXT-7724 Override in LLD when a LLD macro does not exists
- Closed
-
ZBX-16381 Host Discovery rule info: Errors Cannot accurately apply filter: no value received for macro "{#SNMPVALUE}".
- Closed
- mentioned in
-
Page Loading...