-
Type:
Incident report
-
Resolution: Won't fix
-
Priority:
Minor
-
None
-
Affects Version/s: 2.2.21
-
Component/s: None
Please find an example template with a discovery rule attached.
Steps to reproduce:
- Import the attached discovery template.
- Create a host and attach the imported TMPL:APPL:Windows:Mona:Test template
- Send a discovery for the host via zabbix sender for the key: ifx.mona.discovery.processes that contains the following data:
{\"data\":[{\"{#NAME}\":\"Process.exe\",\"{#NAME_WITHOUT_EXTENSION}\":\"Process\"}, {\"{#NAME}\":\"process\",\"{#NAME_WITHOUT_EXTENSION}\":\"process\"} ]}
Full example call:
./zabbix_sender --zabbix-server <zbxserver> --host TEMPLATE_TEST_HOST --key ifx.mona.discovery.processes --value "{\"data\":[{\"{#NAME}\":\"Process.exe\",\"{#NAME_WITHOUT_EXTENSION}\":\"Process\"}, {\"{#NAME}\":\"process\",\"{#NAME_WITHOUT_EXTENSION}\":\"process\"} ]}" --verbose
Result:
The 3 perf_counter["\Process({#NAME_WITHOUT_EXTENSION}) items are missing due to an internal zabbix error
--> the #NAME_WITHOUT_EXTENSION leads to a duplicate key, but the error is not reflected in Zabbix
Expected:
The discovery rule should be marked with an error (as shown in the attached image: no_discovery_error_Process_process)
Note:
When the upper / lower case of the macro is the same the error works -> shown in the other example image: discovery_error_process_process
Easy to reprodue by changing the call to:
{\"data\":[{\"{#NAME}\":\"Process.exe\",\"{#NAME_WITHOUT_EXTENSION}\":\"process\"}, {\"{#NAME}\":\"process\",\"{#NAME_WITHOUT_EXTENSION}\":\"process\"} ]}