other ways to distributed monitoring

[MarcArbour]

Hi.

I know now nodes support has been dropped by zabbix. And proxies doesn't quite do it for me.

I wish to accomplish this setup but with a quirk


Is it possible for the machine called zabbix proxy to operate as a standalone and the machine called zabbix server only show triggered events?

Thus minimizing the traffic between them both.

Any pointers will help.

Thanks a million

So far, my only solution is to script an action that drops a file via ssh on another zabbix server for it to trigger an alert when seeing the file. But this solution is giving me headaches when the ok is sent, I need another script to be run to delete a file instead of creating on but Zabbix doesn't allow that.

[BDiE8VNy]

No, unfortunately not. As the online documentation should have pointed out, a Zabbix proxy queries and receives item values and forwards them to a Zabbix server.
Every processing of these values like trigger evaluation, creating events, triggering actions, ... is done by the Zabbix server.
Anyhow, a Zabbix proxy can be configured to keep a certain period of item values. But that's rather meant to allow local reporting.

There is a promising project announced to be released to the public January 2015: ZabbixUnify - one dashboard to rule them all

Finally you could think about (co-)sponsoring something like "Next generation node based distributed monitoring".