Using v1.1.7, just saw tonight that 1.4 is out, perhaps there are improvements in this area?
Here is my problem, I have 2 point to point wireless units on a tower, and a one to many access unit. I want to set the 2 point to point units as dependencies on the trigger of the access unit (all ping tests). I made triggers for the PP units, which both have an identical dependency (the path to the zabbix server).
All is good so far.
So I try to set the following. Create a trigger for the access unit
Name: {HOSTNAME} Offline (ping for 5 min)
Expr: {AU_CH22:icmpping.max(300)}<1
I've got both the PP units as dependencies which carry in their identical dependency, which generates the error.
[ERROR:Cannot update trigger]
SQL error: Duplicate entry '12369-12370' for key 1
Query: insert into trigger_depends (triggerid_down,triggerid_up) values (12369,12370)
Apparently you can't nest dependencies if the linked triggers have a common dependency? It saves in all, but will it function correctly?
Another annoyance, which I brought up here
You also get an error if you create a trigger that uses a template thats identical to a template in a dependency. I've gotten around this by deleting the template create trigger, and manually making a new one using the hostname rather than the template name in the expression. But of course, it'll create tons of work making individual triggers.
Here is my problem, I have 2 point to point wireless units on a tower, and a one to many access unit. I want to set the 2 point to point units as dependencies on the trigger of the access unit (all ping tests). I made triggers for the PP units, which both have an identical dependency (the path to the zabbix server).
All is good so far.
So I try to set the following. Create a trigger for the access unit
Name: {HOSTNAME} Offline (ping for 5 min)
Expr: {AU_CH22:icmpping.max(300)}<1
I've got both the PP units as dependencies which carry in their identical dependency, which generates the error.
[ERROR:Cannot update trigger]
SQL error: Duplicate entry '12369-12370' for key 1
Query: insert into trigger_depends (triggerid_down,triggerid_up) values (12369,12370)
Apparently you can't nest dependencies if the linked triggers have a common dependency? It saves in all, but will it function correctly?
Another annoyance, which I brought up here
You also get an error if you create a trigger that uses a template thats identical to a template in a dependency. I've gotten around this by deleting the template create trigger, and manually making a new one using the hostname rather than the template name in the expression. But of course, it'll create tons of work making individual triggers.
Comment