Hi all,
Although the following is a bug in 1.4.x and all Zabbix devs are really busy on 1.6, i would like to see the following fixed in 1.4 (small webcode patch i think) as i can't imagine this is a big thing.
Situation
I have multiple triggers with the same trigger name, but different conditions / severities. I want to export and import these templates across several monitoring nodes. I.e.:
- Disk space full {ITEM.VALUE} - {TPL:vfs.fs.size[/,pused].last(0)}>90 - Average
- Disk space full {ITEM.VALUE} - {TPL:vfs.fs.size[/,pused].last(0)}>99 - High
Bug?
When importing the above, the webfrontend sees the first (>99 - Average) as the 'new' trigger and adds it. The second line is seen as an 'update' and the previous trigger gets modified to use >99 - High.
Now, this isn't really a bug i recon, since the import function is made to have this update functionality.
But AFAIK it is zabbix's intention to be able to use the above method, multiple triggers with the same name but different conditions, its the strength of the overview page (multiple colors per box).
solution
I have tried to search for a solution in the webinterface, but i haven't found it yet. Did anyone else fix this by any change (if there is anything to fix).
@devs: What is your opinion on this? Bug or works as designed?
Although the following is a bug in 1.4.x and all Zabbix devs are really busy on 1.6, i would like to see the following fixed in 1.4 (small webcode patch i think) as i can't imagine this is a big thing.
Situation
I have multiple triggers with the same trigger name, but different conditions / severities. I want to export and import these templates across several monitoring nodes. I.e.:
- Disk space full {ITEM.VALUE} - {TPL:vfs.fs.size[/,pused].last(0)}>90 - Average
- Disk space full {ITEM.VALUE} - {TPL:vfs.fs.size[/,pused].last(0)}>99 - High
Bug?
When importing the above, the webfrontend sees the first (>99 - Average) as the 'new' trigger and adds it. The second line is seen as an 'update' and the previous trigger gets modified to use >99 - High.
Now, this isn't really a bug i recon, since the import function is made to have this update functionality.
But AFAIK it is zabbix's intention to be able to use the above method, multiple triggers with the same name but different conditions, its the strength of the overview page (multiple colors per box).
solution
I have tried to search for a solution in the webinterface, but i haven't found it yet. Did anyone else fix this by any change (if there is anything to fix).
@devs: What is your opinion on this? Bug or works as designed?
Comment