Zabbix proxy is a major component in the whole Zabbix architecture. As a result, very often failure of one proxy can lead to dramatic results in all monitoring setup causing a storm of events and problems.
Zabbix proxies allow you to monitor a remote location, a DMZ, and even use cases as using proxies to ‘convert’ passive checks into active or move some load from your Zabbix server towards the proxies is a common solution.
Multi-tenant architecture quite often is a primary requirement. When we think not only about monitoring our own infrastructure, but also about providing monitoring as a service for our customers, many questions come up in terms of design and required software functionality.
Being on duty in a 24×7 IT team might not be fun. Planning duty schedules in Excel, having a shared on-call phone, or searching relevant information in a sea of emails makes it even worse. There is a better way. Integrating the lightweight alerting app SIGNL4 with Zabbix makes the life of an on-call engineer easier, and it allows the IT manager to see what’s going on at any time.
This post outlines how to use Zabbix and iLert with multiple on-call teams, where each team is responsible for a set of host groups in Zabbix, and therefore, will only receive alerts for the services it is responsible for. But first, let’s start with the basic needs when being on-call.
Zabbix supports many different monitoring approaches for different infrastructures. Data collection and analysis are just a part of the job. Once the data is collected, we need to set up proper notification channels and notify end-users of any problems or try and remedy the issues in an automated manner.