PATCH [1.3.6] : "ON" / "OFF" inversion in TRIGGER.VALUE substitution

[Farzad FARID]

Hi,

I think the patch suggested by Dash in another forum (http://www.zabbix.com/forum/showthread.php?t=5679) still needs to be applied to Zabbix 1.3.6, because when a trigger is true it is "ON", right? Therefore {TRIGGER.VALUE} should be set to "ON" in this case.

I have another suggestion too: Would it be possible to apply a mapping of something similar to change the trigger value in the action messages?

In some cases, saying something more explicit, like "CPU load on server XXXX: ALERT", or "CPU load on server XXXX: END OF ALERT" is easier to grasp than an simple "ON"/"OFF".

Regards

[kberrien]

On/off

I have another suggestion too: Would it be possible to apply a mapping of something similar to change the trigger value in the action messages?

In some cases, saying something more explicit, like "CPU load on server XXXX: ALERT", or "CPU load on server XXXX: END OF ALERT" is easier to grasp than an simple "ON"/"OFF".

I totally agree, as I stated in the following thread

http://www.zabbix.com/forum/showthread.php?t=5729

ON/OFF is a bit confusing. I like your ALERT and END OF ALTERT even better than TRUE/FALSE. ON/OFF should be changed, but allowing users to configure their own text would be best...