Strange...it works now if the CRITICAL threshold goes into WARNING threshold I get an WARNING message.
But something's strange now. If the threshold goes directly to CRITICAL, I get a CRITICAL and a WARNING message. The message body is fine so far.
Same back, if it goes from CRITICAL to RECOVER (more than 10% free space), I get a WARNING and a RECOVER message. The message body is strange
The RECOVER message shows the following:
WSUS: Filesystem C: has now 10.863908% remaining
The WARNING message shows the following:
WSUS: Filesystem 10.863908 is low on free space (only C:% remaining)
The variables were switched, but I don't know why.
Please see attached the event processing policy for the HDD allocation
But something's strange now. If the threshold goes directly to CRITICAL, I get a CRITICAL and a WARNING message. The message body is fine so far.
Same back, if it goes from CRITICAL to RECOVER (more than 10% free space), I get a WARNING and a RECOVER message. The message body is strange
The RECOVER message shows the following:
WSUS: Filesystem C: has now 10.863908% remaining
The WARNING message shows the following:
WSUS: Filesystem 10.863908 is low on free space (only C:% remaining)
The variables were switched, but I don't know why.
Please see attached the event processing policy for the HDD allocation