Trying to implement "host dependencies" with "trigger dependencies"
Ok, it's clear: zabbix hasn't got "host dependencies" like nagios, but it could be implemented using "trigger dependencies". Also, "trigger dependencies" are more flexible.
But I've got some questions about this scenario: I've got two routers and some machines. Suppose I have two mail servers machines (smtp1 and smtp2), one behind router A and the other behind router B.
So, when the router A is down, I don't want to receive smtp1's alerts. And, of course, when router B goes down, I don't want to receive smtp2's alerts.
How am I suppose to do that? I think I'd have to add a dependency between smtp1's triggers and router A (trigger 'host is down', or something like that). So, my questions are:
1) I think I'd have to add dependencies "one by one", because I didn't see nothing in the frontend to perform that task easily. Is it right?
2) I suppose I can't do it at template level, because then I couldn't make smtp1 and smtp2 (connected to different routers) inherits from the same template.
Probably I missed something. Any ideas about that?
But I've got some questions about this scenario: I've got two routers and some machines. Suppose I have two mail servers machines (smtp1 and smtp2), one behind router A and the other behind router B.
So, when the router A is down, I don't want to receive smtp1's alerts. And, of course, when router B goes down, I don't want to receive smtp2's alerts.
How am I suppose to do that? I think I'd have to add a dependency between smtp1's triggers and router A (trigger 'host is down', or something like that). So, my questions are:
1) I think I'd have to add dependencies "one by one", because I didn't see nothing in the frontend to perform that task easily. Is it right?
2) I suppose I can't do it at template level, because then I couldn't make smtp1 and smtp2 (connected to different routers) inherits from the same template.
Probably I missed something. Any ideas about that?
Comment