Trigger 'type' field for categorizing triggers

[eger]

I would like to be able to create an action for a group or type of trigger. I think it would be nice to have an additional field for a trigger type. Here is my example for this feature:

I want to create an action for sending a different style message for a service UP/DOWN than an item that is HIGH/LOW, ON/OFF, or just a NOTICE (such as passwd file changed). This was I could make services such as httpd, ftp, smtpd, etc in a 'Services' group and then create an action for a TRUE trigger AND trigger.type = 'Services' and send the appropriate message for UP/DOWN service.

Currently I get messages such as:

Status has changed on the following host: z1.xxxxxxxxxxx.xxx Please see the details below on the service that has been triggered as DOWN:

vfs.file.cksum[/etc/passwd] is DOWN
Severity: Average
Timestamp: 2007.09.13 09:48:04 PST
Event ID: 117 
Host: z1.xxxxxxxxxxx.xxx
IP: 127.0.0.1

In this case I would have a different action message for group 'Checks' (where vfs.file.cksum would be in) that would send a message about it being changed or modified instead of being down.

I had been playing with categorizing using the severities. But I'd rather not give up severity for categorizing.

Hope this makes sense... Anyone else interested in something like this?

[eger]

No one interested in something like this? Bump after nearly year and half

[cstackpole]

I know this has been mentioned before in the discussions about future releases (or at least topics very similar). So there is interest. Also, if I understand properly, the syntax is going to be more flexible in 1.6 to allow for better wording of alerts. What that entails is beyond me at the moment.

Hopefully you will be able to do what you are looking to do in 1.6. Have you kept up with those discussions?

[Alexei]

I think you may use some sort of naming convention for your triggers. Then, in actions, you could configure different actions depending on content of trigger descriptions.

[xs-]

I recently proposed exactly the same thing
http://www.zabbix.com/forum/showthread.php?t=9789 <-- better explained i think.

Some form of trigger categorizing / taxonomy, like the item application (or using item application), this is far more flexible than trigger description (not to mention its esthetically bah ).
Another downside of trigger description is that it must use a text (like) search on the database, which imho is less desirable.

[Alexei]

I recently proposed exactly the same thing
http://www.zabbix.com/forum/showthread.php?t=9789 <-- better explained i think.

Some form of trigger categorizing / taxonomy, like the item application (or using item application), this is far more flexible than trigger description (not to mention its esthetically bah ).
Another downside of trigger description is that it must use a text (like) search on the database, which imho is less desirable.

I absolutely agree. Support of application will be added. As for the text search and most of other action conditions, it works amazingly fast as it does not query database.