Many zabbix-proxy, many zabbix-agent. Stop notification

zabbixzabbix-agent

I have a lot of zabbix-proxy who take care of lot of server with zabbix agent.

Each zabbix-proxy have around 10 zabbix agent under him.

If server who run proxy crash, I got 11 notification (proxy + agent).

Have you a solution for simply receive 1 notification (proxy) ?

I have read theses thread but I have not succeeded in apply them:

I don't understand how to integrate theses information with my configuration already in place.

Thank you.

Best Answer

Under the configuration -> actions menu you can specify to not send an email for a particular trigger/host (for each action you can define conditions). You can create a separate action for this case for exemple.

Related Solutions

Centos – Zabbix Proxy not collecting data

I had this same issue a few weeks ago on a host.

After installing a new host with the zabbix-agent i got the "ZBX_TCP_READ()" in the Zabbix webpannel.

The solution was to change the Server value in the zabbix_agentd.conf to IP instead of HOSTNAME.

The problem originated from a nameserver defined in /etc/resolv.conf that was lagging for some reason.

I don't know if it's related to your problem, but it's worth a try.

Stop Zabbix notification for nodes under zabbix-proxy when proxy service is down

One way to accomplish that would be to monitor whether Zabbix proxy is reachable. This is done using zabbix[proxy,<name>,lastaccess] internal item. In the documentation on internal items, it then suggests to use fuzzytime() trigger function to check availability of your proxy:

{<zabbix>:zabbix[proxy,<name>,lastaccess].fuzzytime(2m)}=0

After that you can make your "host unreachable" triggers depend on this trigger, which will stop them from being activated when proxy is unreachable (see documentation on trigger dependencies for more information).

Best Answer

Related Solutions

Centos – Zabbix Proxy not collecting data

Stop Zabbix notification for nodes under zabbix-proxy when proxy service is down

Related Topic