Distributed Monitoring - Sync'ing templates, triggers, etc

[mucknet]

Hi --

In reading the Zabbix manual, it says that "Configuration Data" is sync'd between Master/Child nodes every 120 seconds. I took "Configuration Data" to mean things like templates, triggers, actions, etc. However, now that I have Distributed monitoring working, it appears that is not the case.

Forum searches aren't turning much of anything either.

What does Distributed Monitoring do besides give me a single GUI to access multiple completely 100% independent zabbix servers?

Does it sync configuration data? Or do I have to manually export/import my templates?

My current zabbix needs are outpacing the hardware we have available (amazon EC2 with a 12 volume EBS RAID volume), so we thought we could turn off history sync, and use Distributed Monitoring to split the monitoring duty between multiple servers without introducing the "human error" risk of constantly exporting/importing templates, copying actions, maintenance windows, etc every time there is a change. Not to mention the huge waste of man hours

Is this what Distributed Monitoring is for?

[qix]

Hi,

It's been awhile since I played with DM myself, but this is what I understand about it:

• It uses multiple nodes that are administered seperatly, possibly by different support groups.
• The nodes have their own seperate configuration
• The nodes can send notifications on their own
• Nodes higher in the tree can see active triggers from lower nodes and can access all information.
• Lower nodes can be administered through the gui interfaces of the higher nodes

If you want to offload monitoring to secondary servers, proxies might be a better option.

See http://www.zabbix.com/documentation/.../proxy_vs_node for the differences between the two.