Component status should be more stateful (status should automatically clear once an issue has resolved itself)
I often repeat the following actions:
- Verify Component Status (Monitoring - System Status - Component Status)
- Open any Component with Status Warning or Error.
- Verify the Warning or Error is Solved
- Reset All Counts for this Component.
A Typical example: Restart the Site Server.
All Management Points complain that the Site Server is unavailable.
But in they also report the System is Online again.
MP File Dispatch Manager running on the management point "mp.company.com" cannot connect to site server "SiteServer.company.com". The operating system reported error 53: The network path was not found.
Component Status Summarizer detected that the availability of component "SMSMPFILEDISPATCHMANAGER" on computer "mp.company.com" has changed to Online.
The Monitoring System could Verify an Error/Warning MessageID was followed by an Information MessageID that indicates the problem has been solved and change the summary status back to OK.