A user noticed this issue before, but I cant find a solution for it.
We learned with 1.6 to harden our monitoring by adding a nodata-trigger for some items to avoid that the item going unsupported unnoticed. This is very important because if a script crashed unexpectedly, the item will become not-supported.
When using 1.8 this does no longer work. If an item gets unsupported time-based trigger-evaluation will also stop.
In our case the host still reports data with agent.ping. But a very important item becomes unsupported and we have no server-side option that assures the item still collects valid data.
bbrendon suggested to "harden" our scripts. This will work on external-checks and userparameter-agent-extensions, but it aint idiot-proof.
It will not work for SNMP-Checks or IMPI-Checks. We saw that certain hosts forget mibs during reboot or IPMI-Sensors get unavailable and you will have no chance to know. Monitoring the unsupported-count is no option. Unsupported items are a common case when using generic templates.
So we need some server-side method to pin items and generate a trigger when its going unsupported. What can we do?
We learned with 1.6 to harden our monitoring by adding a nodata-trigger for some items to avoid that the item going unsupported unnoticed. This is very important because if a script crashed unexpectedly, the item will become not-supported.
When using 1.8 this does no longer work. If an item gets unsupported time-based trigger-evaluation will also stop.
In our case the host still reports data with agent.ping. But a very important item becomes unsupported and we have no server-side option that assures the item still collects valid data.
bbrendon suggested to "harden" our scripts. This will work on external-checks and userparameter-agent-extensions, but it aint idiot-proof.
It will not work for SNMP-Checks or IMPI-Checks. We saw that certain hosts forget mibs during reboot or IPMI-Sensors get unavailable and you will have no chance to know. Monitoring the unsupported-count is no option. Unsupported items are a common case when using generic templates.
So we need some server-side method to pin items and generate a trigger when its going unsupported. What can we do?