Hi,
After my whole exploration of how escalations and recovery messages work (http://www.zabbix.com/forum/showthread.php?t=11433), I thought of two things that could add more flexibility.
Img 1
Replacement of default recovery message
When you edit an operation you can choose not to use the default message by unticking the box and then filling in a replacement subject and message body.
It would be nice if one could do the same with the recovery message.
Why?
Lets say you send a notification to an email address in Step 1; here you put in lots of details of the incident since its email. Then in Step 2 (the escalation after time period) you want to send an escalation message to a cellphone. But because one text message is limited to around 160 characters, you do not use the default message and fill in a replacement message which is shortened version.
You might also want to have a shortened version of the recovery message that will go to the cellphone?
Currently I just have a short default recovery message, which seems to work good enough. Will see over time.
--
Img 2
More control over logic in conditions
In img 1 you can see what it currently looks like when you setup the conditions for the action. If I choose "AND/OR" it will fill do it as shown. If I choose "AND" everything becomes 'and' [ (a) and (b) and (c and d and e) ]. With 'or' everything becomes 'or' [ (a) or (b) or (c or d or e) ].
But what if I want to have
[ (a) and (b) and (c or d) and e) ]
Zabbix doesn't allow this at the moment?
With this screenshot I might want to have logic that does the following:
ACTION A
I would setup another action
ACTION B
So some items might be marked with only 'A_BACKEND' and some might be marked with 'A_BACKEND' and 'A_NOT247'.
This way I can differentiate between them and setup actions accordingly.
But then again, maybe there's another solution
After my whole exploration of how escalations and recovery messages work (http://www.zabbix.com/forum/showthread.php?t=11433), I thought of two things that could add more flexibility.
Img 1
Replacement of default recovery message
When you edit an operation you can choose not to use the default message by unticking the box and then filling in a replacement subject and message body.
It would be nice if one could do the same with the recovery message.
Why?
Lets say you send a notification to an email address in Step 1; here you put in lots of details of the incident since its email. Then in Step 2 (the escalation after time period) you want to send an escalation message to a cellphone. But because one text message is limited to around 160 characters, you do not use the default message and fill in a replacement message which is shortened version.
You might also want to have a shortened version of the recovery message that will go to the cellphone?
Currently I just have a short default recovery message, which seems to work good enough. Will see over time.
--
Img 2
More control over logic in conditions
In img 1 you can see what it currently looks like when you setup the conditions for the action. If I choose "AND/OR" it will fill do it as shown. If I choose "AND" everything becomes 'and' [ (a) and (b) and (c and d and e) ]. With 'or' everything becomes 'or' [ (a) or (b) or (c or d or e) ].
But what if I want to have
[ (a) and (b) and (c or d) and e) ]
Zabbix doesn't allow this at the moment?
With this screenshot I might want to have logic that does the following:
ACTION A
IF [App Dev Host Group]
AND
[JBOSS Availability trigger fires]
AND
( [for items marked with A_BACKEND] OR [items marked with A_CALCULATIONS] )
AND
[for items marked with A_NOT247]
AND
[time is between 06:00 and 18:00]
THEN <fire action>
AND
[JBOSS Availability trigger fires]
AND
( [for items marked with A_BACKEND] OR [items marked with A_CALCULATIONS] )
AND
[for items marked with A_NOT247]
AND
[time is between 06:00 and 18:00]
THEN <fire action>
I would setup another action
ACTION B
IF [App Dev Host Group]
AND
[JBOSS Availability trigger fires]
AND
( [for items marked with A_BACKEND] OR [items marked with A_CALCULATIONS] )
AND
[JBOSS Availability trigger fires]
AND
( [for items marked with A_BACKEND] OR [items marked with A_CALCULATIONS] )
So some items might be marked with only 'A_BACKEND' and some might be marked with 'A_BACKEND' and 'A_NOT247'.
This way I can differentiate between them and setup actions accordingly.
But then again, maybe there's another solution
Comment