I had a problem this week when I was trying to run some reports in OpsMgr 2007 R2. Some reports were failing … either issues to do with “LT_Report”, missing parameters or internal failures. If I played with the time settings for the report criteria then sometimes I’d get a result but not the one I was chasing. The SQL Reporting database is running on SQL 2005. I upgraded it to SP3 and that fixed the issue – I’m a bit hesitant about installing SQL service packs.
I really like the reporting feature of SCOM. The reports in MOM 2005 always struck be as a bolt on. Information and reports are an integral component of OpsMgr 2007 and 2007 R2. You can navigate to just about any item in the monitoring view of the Operations Console and get a context sensitive link to the report console in the Tasks pane.
Reports can have hyperlinks to view further material. For example, this week I’ve run availability reports on Hyper-V virtual machines, physical hosts, operating system installations and web sites. A client asked about the uptime of a website on a server. Bang: out came a report showing 100% up time.
You can build on this with Distribute Application modelling and the SLA (Service Level Agreement) module. This allows you to get the ITIL view of your services (not windows services but services provided to users/customers). You can then run reports on the SLA compliance. How sweet is that?