Hello Zabbix People.
We use Zabbix since 2013 and want to take it to the next level. Currently I'm digging into the global event correlation mechanisme and I'm finding it hard how to work around some issues.
I will use a basic test case concering disk space usage on a single host but I think this will be the case in many more scenarios.
The test case:
I have made 2 triggers concerning disk usage in percentage. One 20% and one 10% of free space on disk. I have tagged the triggers with:
Trigger one Tag: Disk Free Percentage
Value: 20
and
Trigger two Tag: Disk Free Percentage
Value: 10
After this I went on creating a global event correlation which states that when the "Old event tag Disk Free Percentage equals 20" by the "New event tag Disk Free Percentage equals 10" it should "close old events"
The reasons is that we don't want to see events/problems that aren't relevant anymore concerning disk space. Because when the 20% trigger and the 10 trigger fires, only the 10% is relevant.
This works so far. The 20% trigger gets deleted when the 10% trigger is active, but,..a new 20% trigger event fires after a new check round, leaving us, with again, two active triggers, the 20% and 10%. Ofcourse this is a natural way Zabbix works because the disk still
has less then 20% of free space and creates a new event.
Thus my question:
Is there a way we don't get a trigger when a smaller threshold is crossed?
We use Zabbix since 2013 and want to take it to the next level. Currently I'm digging into the global event correlation mechanisme and I'm finding it hard how to work around some issues.
I will use a basic test case concering disk space usage on a single host but I think this will be the case in many more scenarios.
The test case:
I have made 2 triggers concerning disk usage in percentage. One 20% and one 10% of free space on disk. I have tagged the triggers with:
Trigger one Tag: Disk Free Percentage
Value: 20
and
Trigger two Tag: Disk Free Percentage
Value: 10
After this I went on creating a global event correlation which states that when the "Old event tag Disk Free Percentage equals 20" by the "New event tag Disk Free Percentage equals 10" it should "close old events"
The reasons is that we don't want to see events/problems that aren't relevant anymore concerning disk space. Because when the 20% trigger and the 10 trigger fires, only the 10% is relevant.
This works so far. The 20% trigger gets deleted when the 10% trigger is active, but,..a new 20% trigger event fires after a new check round, leaving us, with again, two active triggers, the 20% and 10%. Ofcourse this is a natural way Zabbix works because the disk still
has less then 20% of free space and creates a new event.
Thus my question:
Is there a way we don't get a trigger when a smaller threshold is crossed?
Attached Files
Comment