Creating persistent dashboard issues

[stefstef]

Hi

I've been trying to setup file checksum events in my Zabbix 1.6.2 installation, using the predefined triggers ({device:vfs.file.cksum[file].diff(0)}>0). The problem with this approach is that if the checksum changes an issue is only raised in the dashboard until the next file checksum is polled. Is there a way of making the issue "sticky", i.e. force it to be active until it's acknowledged?

Kind regards
Stebbi

[froztbyte]

Hi

I've been trying to setup file checksum events in my Zabbix 1.6.2 installation, using the predefined triggers ({device:vfs.file.cksum[file].diff(0)}>0). The problem with this approach is that if the checksum changes an issue is only raised in the dashboard until the next file checksum is polled. Is there a way of making the issue "sticky", i.e. force it to be active until it's acknowledged?

Kind regards
Stebbi

I've also been looking around. If this doesn't exist yet, it could make an excellent addition to the featurelist for 1.8. Best would be to make it available on a per-trigger basis and not as a global, otherwise we'd possibly sit with a bunch of "mostly for knowing" triggers that we have to acknowledge to get out of our sight, like perhaps 10% packetloss warnings (which is perhaps not all that uncommon).

[Alexei]

I think you may use hysteresis triggers, i.e. triggers having different conditions for TRUE and FALSE states.

[froztbyte]

I think you may use hysteresis triggers, i.e. triggers having different conditions for TRUE and FALSE states.

Something like this could work, but I can't see how to determine if the trigger has been acknowledged from the macros listed in the documentation. Oh, the version I'm running here is 1.6.2/1.6.4.

[Alexei]

Something like this could work, but I can't see how to determine if the trigger has been acknowledged from the macros listed in the documentation. Oh, the version I'm running here is 1.6.2/1.6.4.

Currently there is no way to determine if the trigger (event actually) was acknowledged or not.

[froztbyte]

Currently there is no way to determine if the trigger (event actually) was acknowledged or not.

So, somewhat hacky, but I've made some headway on how to make this work. Create a second action that runs a script that takes {EVENT_ID} and does a database query for getting the acknowledged status of the trigger in question. From here I'm going to try two options.

Option 1 is see if I can find some way to make a self-reference to this on the existing trigger/item (but I don't think I can).
Option 2 is to update another item and make that then come up as an alert as well. Won't send out any notifications but the first trigger will become dependent on this one or something and I'm going to try to make this work as I need it to during the day tomorrow. Any recommendations or ideas welcome. Also, I've put this in as a feature request for 1.8, since having it in-Zabbix would be the much more welcome way of doing this.