Seperating network & host issues with dependancies

[FonTim]

Hi all,

I am planning to use Zabbix to monitor accross several datacenters and had planned on using a proxy in each DC to 'spread the load' a little.

What I don't understand is how I can have templates applied to hosts in different DCs, with their triggers dependant on their proxy. On top of this I have been asked to be able to seperate network/host issues so a trigger for the proxy should not fire if it is the VPN tunnel to the datacentre that is down for example.

Example:

               CENTRAL DC
                   |
               VPN Router
                   |
  +----------------+----------------+
  |                                 |
 DC1                               DC2
  |                                 |
  +----+----+             +----+----+
  |    |    |             |    |    |
  |    |  Host 2       Host 3  |    |
  |  Host 1                  Host 4 |
DC1 Proxy                      DC2 Proxy

• Host 1 & 2 are monitored via DC1 Proxy.
• Host 3 & 4 are monitored via DC2 Proxy.
• Host 1, 2, 3, & 4 all have a 'System' template with various items & triggers (inc. nodata triggers).
• The VPN Router is monitored directly in CENTRAL DC with items for the tunnels, and triggers if they fail.
• The triggers of the hosts need to be dependant on their proxy, which in turn needs to be dependant on the VPN link.

As I understand it, I cannot make a template trigger dependant on a host trigger, so I am very unsure as to how I can configure my hosts, templates, triggers, and so on in order to achive this setup.

Many thanks for any suggestions.

[neogan]

For example:
In central DC you can use zabbix_server
for DC1 you can use zabbix_proxy DC1.
for DC2 you can use zabbix_proxy DC2.

Create two different or similar template for hosts with different name.
and use for example discovery rule for 1 dc though its proxy and action use create host and link to its template.

for another DC you can use another discovery rule.

[FonTim]

Thanks for your input neogen, but I still don't understand how that applied to trigger dependancies...

And the whole point of creating these templates is that I can use the same template across hosts in all datacentres. If I have to create seperate templates for each, I might as well not use templates at all (we currently have plans for equipment in 10 seperate centres).

[erisan500]

Did you ever resolved this? I'm in a similar situation too.