How can I put triggers (as opposed to hosts) into maintenance?

[funkypenguin]

Hi all,

I'm trying to replace Nagios with Zabbix, and one issue I'm stuck on is maintenance for triggers..

I.e., I may want to put the "Free disk space on C:" trigger into maintenance for a week, while I have my team work on a resolution, but I wouldn't want to put the entire host into maintenance, because then I wouldn't get alerts about anything else (unexpected) going wrong on the host.

Is there a way to work around this?

Thanks,
D

[danrog]

What we do (so we know its still an issue when looking at the dashboard or triggers page) is simply acknowledge the trigger and have the alert actions setup so it won't alert once acknowledged (you can do this by setting a filter on the action step). This also enables you to follow up with the person that acknowledges the alert in case you wanted to know what was going on with it (we have a global team so this makes it easier for us to track down who is working on the issue). If you really wanted to go crazy you could also setup action steps that execute far in the future just to give people a nudge so its not forgotten about (I wrote a simple perl script that emails the team weekly on ALL open issues just so they're not forget about )

This is a different approach from Nagios but then again, Zabbix is very different when compared to Nagios

[Hansi]

Hi,

welcome to the club of Nagios refugees
Don't be afraid - you will see that zabbix is much better than Nagios...First I was also lost but now I love it so much!

But that was not your question.

Well the answer of Danrog works if your disk space does not change very often. From my point of view in your case I would just deactivate the item on this host for this period manually (don't forget to activate it again).