Critical Rising Threshold Exceeded notification mail

[Sakti Chakravarty]

We have disk threshold monitoring set up on our Windows servers so that we are emailed when Warning or Critical disk usage levels are exceeded.

The Warning email contains this text in the body of the email:

----------------
Details:
SNMP Object Identifier '.1.3.6.1.4.1.232.11.2.4.1.1.5.2'
Threshold Type 'ABSOLUTE VALUE - NO FALLING'
Current Value 92
Rising Threshold 75
Owner 'Insight Web Agent'
Severity 'WARNING'
Description 'E:DataDisk1 [NTFS] disk space'
----------------

but the Critical email has no information under "Details". This makes it difficult to determine which threshold has been exceeded.

This used to work previously, I get the feeling something has changed with the Foundation Agents. We recently upgraded all our Agents to Support Pack 7.30A ... has anyone else encountered this problem?

[Alexander Glass]

Isn't it saying that your E: drive is using 92% and the threshold is 75%?

[Sakti Chakravarty]

Yes, the Warning threshold is set at 75%, and the Critical threshold is set at 95%.

I've pasted the information from the Warning email, the problem is that the Critical email contains no such information.

[tmagee]

I can't help directly with your issue, but on a related topic are you finding your disk alerts have worked as intended aside from this issue?

I'd raised a topic on the forum ("disk threshold falling alert not generated, not reset" on Feb 1, 2005), where I could get a warning and critical message for disk space rising, but once only and no falling alerts at all when the disk space is free again.

So, when disk space is below the reset the value then disk used space made to rise again I would not get an alert. I've tried later versions of SIM and agents since then with no success, but I guess in terms of your issue, the critical message did get created with the revisions I had. It would be interesting to know if you have experienced this issue of no falling alerts as I suspect the agents relating to disk alerts and disk space have a bug somewhere.