Agent status triggers

[iaingblack]

Hi guys, I am having some issues with agent triggers. Basically, we have a WAN link with some servers in another site and the agent status test response on some of the servers seems to get lost and they appear to be down when they aren't.

So, this is what I have tried. my trigger used to be;

{CT_Windows_Server_Test:status.last(0)}=2

This was fine but gave the rroneous hosts down so I did this

{CT_Windows_Server_Test:status.last(0)}=2 & {CT_Windows_Server_Test:status.last(1)}=2

I was hoping this would only trigger on two satus errors in a row but it still seemed to happen. Can I just chain these indefinitely and hope it can survive the bumps?

As an alternative, I tried this in the hope it would only fire if the status was like this for 300 seconds or longer but, it would still fire and then I seem to miss recovery messages, which makes things worse as it makes me paranoid! But, I still get the alerts anyway so it didn't solve anything.

{CT_Windows_Server_Test:status.max(300)}=2

Does anyone have any advice on what I could be doing wrong? I seem to be really struggling to get a decent way of buffering the odd the errant result out of the system. My checks refresh interval is every 60 seconds if that helps any.

Cheers!
Iain

[wizard-ict]

{CT_Windows_Server_Test:status.max(300)}=2 will fire if 1 or more values is 2, as that will be the maximum value, so that isn't really what you're looking for.

You could use {CT_Windows_Server_Test:status.min(300)}=2 which should only trigger if every value is 2 (or higher).

You could also use {CT_Windows_Server_Test:status.avg(300)}=2. Only if every value is 2 will the average also be 2 (given that the only possible values to receive are 0 and 2) though in theory working out an average should use more processing power than simply looking for the min value

[iaingblack]

Ahhh, great, thanks Wizard! Setting it as min 2 makes sense after a bit of though, didn't think of it that way before!