When we look at this particular Zabbix instance we are working with around 400 network devices. Monitoring routers, switches and firewalls takes a lot of items and thus alerting can be tricky to setup and maintain.
In big networking environments like the one we are working with here it is important that alerting is handled with great care to make sure engineers aren’t overloaded with them. Only the highest priorities should actually be handled 24x7x365 by engineers. You do not want to overload your engineers with alerts, especially not in their personal time. A happy engineer is a happy network in this case!
Most of the alerting issues can be handled by setting up alerting in Zabbix correctly, better yet it is even still very important when setting up Opsgenie. Opsgenie will handle your centralisation, your scheduling and your alerting but it will only alert what you send to it, thus making a solid Zabbix Server still very much a requirement.
We are going to use Opsgenie as a gateway between certain alerts, engineers and even customers.
<blockquote>Keep reading about Zabbix and Opsgenie integration at the Zabbix blog:
https://blog.zabbix.com/scheduling-and-escalation-made-easy-zabbix-and-opsgenie-integration/10005/</blockquote>