How to avoid trigger spam

[guest6936]

Hello,

I am new to Zabbix and haven't quite yet hit the sweet spot for us. For an example we have a trigger that checks the available disk space on a harddrive. It triggers if the available space is 15% or less than 15%

It looks like this

last(/Template/vfs.fs.size[/,pfree])<={$DISK.SPACE.WARN}

Our problem is when hosts are pending between 15-16% available space and it causes a lot of alerts. How would one go about to tackle this?

[vitS]

Hi,

Are You talking about trigger configuration, like

PROBLEM event generation mode

• Single
• Multiple

It should be Single

Thanks,

[guest6936]

Hi,

Are You talking about trigger configuration, like

PROBLEM event generation mode

• Single
• Multiple

It should be Single

Thanks,

Thanks for your reply. All our triggers are Single already but the issue is that triggers pending between PROBLEM <-> RESOLVED.

The disk jumps 15-16% free and each time it hits 15% it generates an alert, then it go back up to 16% and the problem is resolved, then 15 minutes later it can go down to 15% again and the circle of life continues.
I am thinking if there is a smarter way to do this to reduce the amount of alerts. The most obvious reason is of course to release some disk space so it is no longer on the edge but it requires us to plan maintenance and before that is done Zabbix will continue to hammer us with these edge alerts.

[vitS]

Hi, You can put trigger as < 15 and add in trigger recovery expression like > 15 and also can be added ,#2 in trigger expression ( like if expression was triggered 2 times )

[guest6936]

Hi, You can put trigger as < 15 and add in trigger recovery expression like > 15 and also can be added ,#2 in trigger expression ( like if expression was triggered 2 times )

I am wondering if this is the best approach. The issue comes back in other scenarios as well. Perhaps it would be good to check if the status has been the same for the last X tests than we raise the alert

Like this
last(/host/key,#2-3)

But I think this is a good discussion because I do not know the best approach for such checks.

[guest6936]

For now I added a recovery expression so that the warning will not release until it has 20% free disk space. Maybe this is the solution indeed?

[vitS]

Hi,

Yes this one should help to avoid spam.

[cyber]

If that default limit is in a place, what is not for you, just change it to what is comfortable for you .. {$DISK.SPACE.WARN} macro in template (or override it on host level for specific host).
But what you already did is also a good approach, making sure that something is actually done about disk space..