Missing TRIGGER.THRESHOLD

[apiero]

Hi there,

as email sent by zabbix if some trigger is triggering I'm using something like:

{TRIGGER.NAME}: {STATUS}
{TIME} {DATE}
{HOSTNAME}:{IPADDRESS}

{EVENT.ID}

{ITEM.NAME}
{ITEM.LASTVALUE}

{STATUS}
{TRIGGER.COMMENT}
{TRIGGER.ID}
{TRIGGER.KEY}
{TRIGGER.NAME}
{TRIGGER.SEVERITY}
{TRIGGER.STATUS}
{TRIGGER.URL}
{TRIGGER.VALUE}

just to get every possible information zabbix can give to me.
In all these macros I personally miss the macro TRIGGER.THRESHOLD that should tell me which was the threshold trepassed by the trigger: can you consider to add it? Does it make sense to you?
Is it also possible to have the real trigger expression? Say I have an item defined as

system.cpu.load[,avg1]

and the trigger is

{Template_Linux:system.cpu.load[,avg1].min(900)}>5.5

how can I get this expression? Is it possible to add the macro TRIGGER.EXPRESSION as well?

Many thanks for your wonderful work!
Bye
Piero

[eger]

I am surprised no one responded to your request.

I would also love to have macros for the trigger threshold (>5.5 part) and the full expression.

In my emails I have the current ITEM.VALUE. But knowing how much over or under this value is from the trigger is unknown without logging in and looking at the trigger. Would be nice to be able to see that the ITEM value was 11.7 and the THRESHOLD was >5.5 in the email.

I agree they could be TRIGGER.THRESHOLD and TRIGGER.EXPRESSION. Don't see why this shouldn't be possible. Hopefully Alexei can see this post.

I hope we are talking about the same thing

[StefanJ]

I also missing TRIGGER.THRESHOLD for mail. This information ist important for the user who get the message.

[richlv]

this might be tricky oince you consider more advanced expressions. what should those macros expand to for a trigger like {a>1} & {b<2} ?
the idea itself is interesting, but you should, if possible, write in detail, how would such macros behave in other cases than the most simple trigger expressions.

[StefanJ]

On our current monitoring system (NetIQ) we generate automatically messages like:

Low space on drive c:

Value   |  Threshold
-------------------
92 %    |  90%

This is a important information for the responsible application manager.

Also we import parameters like this from our selfmade CMDB periodical. This is very smart to interact with the other departments in our company. So we hope there is a good API in the comming version 1.8, too.

I hope we get the same functionality with Zabbix for the future.

[richlv]

as i said, i don't see how this could be sanely implemented with the flexible trigger expressions that zabbix offers.
as a workaround, you can try including thresholds in the trigger names - that's what i do...

[simonc]

as i said, i don't see how this could be sanely implemented with the flexible trigger expressions that zabbix offers.
as a workaround, you can try including thresholds in the trigger names - that's what i do...

Or in the {TRIGGER.COMMENT} field...