may you consider in a future release to simplify the trigger creation ?
when using zabbix, like other monitoring software, your aim [most of time ] is to get working the 3 following :
1) define a ressource [ items in zabbix ],
2) monitor ths ressource [ triggers in zabbix ]
3) get inform of problem [ actions in zabbix ].
for my point of vue, points 1) & 2) are very long to create.
point 3) if wonderful & so simple
So, could you take one of those solutions to help simplify ?
a- give the possibility to create trigger on the same screen as items [ why not with trigger templates beeing associated with items ]
b- keep the trigger creation in a specific screen, but give it the same possibility as when creating a action [ items name like ... ]
to illustrate, take the follwing exemple :
1) need to monitor the %free space on many many file system
2) want a trigger that get UP when %free space < 20.
if the items for filesystems are all created with the same naming convention [ filesystem /toto, filesystem /titi ], it'll be easier to create just ONE trigger base on items name like 'filesystem*' ??
when using zabbix, like other monitoring software, your aim [most of time ] is to get working the 3 following :
1) define a ressource [ items in zabbix ],
2) monitor ths ressource [ triggers in zabbix ]
3) get inform of problem [ actions in zabbix ].
for my point of vue, points 1) & 2) are very long to create.
point 3) if wonderful & so simple
So, could you take one of those solutions to help simplify ?
a- give the possibility to create trigger on the same screen as items [ why not with trigger templates beeing associated with items ]
b- keep the trigger creation in a specific screen, but give it the same possibility as when creating a action [ items name like ... ]
to illustrate, take the follwing exemple :
1) need to monitor the %free space on many many file system
2) want a trigger that get UP when %free space < 20.
if the items for filesystems are all created with the same naming convention [ filesystem /toto, filesystem /titi ], it'll be easier to create just ONE trigger base on items name like 'filesystem*' ??
Comment