There's a "rule of monitors" that a user of scom might be aware of. If you have an alert that was generated by a monitor (as opposed to a rule that generates alerts) do not close it and let it close it self. If you do close the alert you wont be notified of the issue again until the monitor returns to a healthy state and then goes back into an unhealthy state.
If someone closes an alert for disk space (or if it occurs during maintenance, or it's old and gets auto closed) we don't find out the server still has space issues until the machine has problems. I'd like a way to regenerate alerts for monitors that are in an unhealthy state.
Currently I've looked at a powershell solution called GreenMachine but it doesn't seem to work very well and is very very slow.
What solutions have people found to this problem?
Best Answer
An easier solution, though with a higher impact: put the object generating the critical health state in maintenance mode for 15 minutes. The health state will change to "not monitored" an will be re-evaluated once it quits maintenance mode.
This way you will regenerate an alert. Bear in mind though that it will have the same effect for every rule an monitor running on that object.