Sometimes it's good to have a list of SCOM alerts mailed out, especially if your SCOM environment is not connected to a job management system. In our environment, we email out a list of alerts that are in the "New" resolution state, as a gentle reminder for people to sort it out.
Self-plug : I will be doing a joint presentation at Microsoft Ignite NZ in September on OMS, and analysing your data in the cloud. Come to the session if you want to hear more about OMS being used in real life. http://msignite.nz
Microsoft recommends that machines loaded into Microsoft Operations Management Suite (OMS that are running IIS, have their log rollover set to hourly. http://blogs.technet.com/b/momteam/archive/2014/09/19/iis-log-format-requirements-in-system-center-advisor.aspx
However, once machines are added into OMS, it's entirely possible the IIS logs are changed, new sites are rolled, etc. And there is no easy way to see if that had been done, or stay on top of it.
As a solution I throw an alert in SCOM if any site is not configured to 'hourly'.
See my TechNet wiki articlefor a howto, and a handy script to set up IIS Log rollover via PowerShell.
I published an article about displaying OMS updates in SCOM. Looks like I picked up the gold award System Centre from the Technet Wiki Ninja's. yay! http://blogs.technet.com/b/wikininjas/archive/2015/07/17/the-microsoft-technet-guru-awards-june-2015.aspx
OMS (Microsoft Operations Management Suite) pushes management pack updates automatically down to your on-premise SCOM, as part of Microsoft's rapid releases. Unfortunately there is no easy way to see when this happened, so *if* something broke - it's harder to associate with a change.
(change control - time for a rethink?)
I threw together this script to query the SCOM database and return any MP updates in the last 24 hours. And then built an alert in SCOM to tell me if it had any results from that script.