So here's my issue... I have my triggers tuned pretty well, except for ONE specific use case, and I'm hoping that there is a simple way to get this accomplished without editing EVERY SINGLE trigger that I have.
Trigger notifications work perfectly well except for the specific instance of a power outage. When a power outage happens, all hell breaks loose because things can't communicate, etc. This is expected, but I'm hoping there is a way to stop it based on the status of another item. I have a UPS connected, and I monitor that as well. So basically, I want Zabbix to act exactly as it is at all times, except when UPS.Status == 0. When UPS.Status == 0, all I want is the initial notification for THAT trigger (which lets me know the power is out), and not the several hundred that appear after that related to things being disconnected, etc.
Has anyone else come across this? This must be a pretty standard use case, but maybe it's not. I think I'll still get flooded when all the triggers change to "OK", but perhaps there's a way to determine when the UPS.Status went from 0 to 1, and if that time is > 30 min, then don't send any of the "OK" triggers.
I believe that in essence this is accomplish-able (I have all the data I need I believe), but I'm not sure how I would do this with as little impact as possible. I've seen it recommended to add the condition to the other triggers but this would require hundreds and hundreds of modifications.
Any hints would be awesome. Thanks!!
Trigger notifications work perfectly well except for the specific instance of a power outage. When a power outage happens, all hell breaks loose because things can't communicate, etc. This is expected, but I'm hoping there is a way to stop it based on the status of another item. I have a UPS connected, and I monitor that as well. So basically, I want Zabbix to act exactly as it is at all times, except when UPS.Status == 0. When UPS.Status == 0, all I want is the initial notification for THAT trigger (which lets me know the power is out), and not the several hundred that appear after that related to things being disconnected, etc.
Has anyone else come across this? This must be a pretty standard use case, but maybe it's not. I think I'll still get flooded when all the triggers change to "OK", but perhaps there's a way to determine when the UPS.Status went from 0 to 1, and if that time is > 30 min, then don't send any of the "OK" triggers.
I believe that in essence this is accomplish-able (I have all the data I need I believe), but I'm not sure how I would do this with as little impact as possible. I've seen it recommended to add the condition to the other triggers but this would require hundreds and hundreds of modifications.
Any hints would be awesome. Thanks!!
Comment