-
Incident report
-
Resolution: Duplicate
-
Critical
-
None
-
2.2.7, 2.4.1
-
None
-
Debian 6 X64 on server, proxy and frontend in separated servers
-
Team A
-
Sprint 49 (Feb 2019), Sprint 50 (Mar 2019)
I created a template.
Inside the template I created an item external script.
The script returns a value of 0 to 512.
This same item is set to unsigned decimal.
Within this same template I created a trigger that is triggered when the maximum value of the last 180 samples is 0.
My configuration is distributed, ie, have a zabbix zabbix server and a proxy on an external site.
Put this external script within the correct folder on the zabbix proxy server.
Created a host and configured to be monitored by the same proxy server's external drive.
Assigns that host the template mentioned above.
The problem occurred and did not find a solution.
Here's the problem:
When this item quoted above became "not sopported" in a given collection to its respective trigger became "unknown".
Spent more than 180 collections thus leaving the item "supported" and the trigger has not ceased to be "unknown".
What can it be?
Thank you for listening
Renato Lopes