Action messages

[ari]

With 1.9.7, the default action messages look like this:

Trigger: ping failed to host 'SCC Camperdown'
Trigger status: PROBLEM
Trigger severity: High
Trigger URL: 

Item values:

1. ping (SCC Camperdown:icmpping): 0
2. *UNKNOWN* (*UNKNOWN*:*UNKNOWN*): *UNKNOWN*
3. *UNKNOWN* (*UNKNOWN*:*UNKNOWN*): *UNKNOWN*

I like the idea that we can show multiple items in the message, but all those UNKNOWNs are a bit confusing. Is there a way to customise the message to only show as many items as are relevant? For other triggers, having two or three items might be very nice. But 99% of them are simply one item.

[richlv]

those should be last 3 values, so if you have only one, others are unknown. i definitely agree that it doesn't look nice, but i don't know of a simple solution.
a fairly complex one would be to have some sort of a variable expansion like bash has, or some if/then syntax which could hide values and additional text...

[ari]

Don't know what you mean by 'last 3'. I've only ever seen one in there, even for items that have been collecting data for a long time.

Is this related to the bug we found where nodata(1000) returns rubbish results?

We are running 1.9.7 still because 1.9.8 has broken mysql upgrade scripts.

[richlv]

Don't know what you mean by 'last 3'. I've only ever seen one in there, even for items that have been collecting data for a long time.

hmm. if you look at the history for those items, do the values show up ?

Is this related to the bug we found where nodata(1000) returns rubbish results?

i don't think it should return "rubbish results"... what do you mean by that ?

We are running 1.9.7 still because 1.9.8 has broken mysql upgrade scripts.

broken how exactly ?

[richlv]

hmm. if you look at the history for those items, do the values show up ?

argh, ignore this. by default, it will show last value for the first 3 items, used in the trigger expression - if your expression doesn't use more than one item, it will always be only one value, of course

[mike smith]

surely there must be a way to fix this. we're in the middle of eval'ing a new monitoring system, and this is one of the bigger issues i'm hearing about from some of the higher ups.

if anyone can point me to the code that is responsible for the generation of the alert email, i'll give it a shot at coming up with a patch to resolve this admittedly only cosmetic issue.

[richlv]

well, the simplest solution - just remove those few lines which include last values (in action properrties)...

[mike smith]

interesting idea. might you know off hand how many stock triggers in the stock templates use more than one item? all the custom ones i've created are only using a single item, so this might be the easy fix for us.

[richlv]

a couple at most - like checking for possible different apache/syslog process names

[mike smith]

thanks, i appreciate the speedy insight.