Custom Operations Manager Reports
Based off of a recognized demand, I developed a management pack that provides three key reports for Operators and Administrators to leverage. These reports were based off of queries developed by Kevin Holman and Jonathan Almquist and tuned to support these reports. The three reports that I have included in this MP are:
- Maintenance Mode - Agent-Managed Systems in Maintenance: This report will show the agent-managed systems that are currently in maintenance in the management group.
- Maintenance Mode - History of Maintenance for Agent-Managed Systems: This report will show the history of Maintenance Mode activities in the management group for agent-managed systems. and rollup total duration for those systems based on the date/time parameters the report will query within. This report is based off of an example report that was demontrated by us at MMS back in 2009. I used this as a foundation for learning to develop custom reports using Report Builder.
- Management Group Health Report - This hygiene report evaluates key performance metrics that help identify management packs that require additional tuning (discovery, monitors, and performance/alert rules) to ensure optimal health and performance of the management group. Sure you get this information today by a couple of built-in reports (I don't have access to OM now to reference those specific reports, so please bear with me), but you need to select the specific management packs and other relevant parameters. Here we have a single report to run to summarize that information as a starting point, and you can use the other built-in reports to further evaluate and determine if additional tuning efforts are required.
No manual steps are required once you import this MP. The reports are running against the Data Warehouse database, so you don't need to create a custom data source.
Comments
Anonymous
January 01, 2003
Can you put up a couple screenshots of the reports?Anonymous
January 01, 2003
I should have pointed out a while ago that I developed and tested these reports against SQL 2008 and 2008 R2, not SQL 2005. I'll go back and modify the report schema to support SQL 2005 and test before publishing a new version.Anonymous
January 01, 2003
You beat me to it. I was going to post something similar very soon. Maybe I still will :)Anonymous
January 01, 2003
Upgrading DWH to SQL 2008R2 sems to have fixed the issue for me.Great Reports..ThxAnonymous
January 22, 2012
Very useful ... thanks!Anonymous
January 22, 2012
Sounds great. I was going to try it out in our lab but get an error on import "This assembly is not fully signed. Cannot verify the Strong Name ". br LAnonymous
January 23, 2012
Imported this MP, but only the directory 'Operations Manager Health Reports' is shown in the 'Reporting' node and not the actual reports. Any pointers?Anonymous
January 25, 2012
Ramesh - depending on the amount of activity in your MG, it takes a few minutes for the reports to get uploaded to the SQL server hosting SQL Reporting Services after you import the MP.Anonymous
January 26, 2012
Matt - I waited for long time. In fact in the reporting page, it shows that there are no items in that folder. Its been two days now. I verified in the Authoring Console that these reports are visible (set to TRUE) SQL Server Reporting Services Home > OperationsManager.Health.Reports Home | My Subscriptions | Help There are no items in OperationsManager.Health.Reports. Click Help for more information about this page.Anonymous
January 26, 2012
Matt, Am also noticing the same issue with the Reports.Anonymous
January 26, 2012
Ramesh and M.Mathew - can you check the Operations Manager event log on your RMS and look for error level events from the source Health Service Modules? E-mail me directly at mgoedtel@microsoft.com when you find the related event so I can review it. I have imported this MP in four different environments during and after testing and have not exprienced this behavior. ThxAnonymous
January 27, 2012
The comment has been removedAnonymous
May 02, 2012
Has anyone figured out why these reports dont deploy in some environments? I too am getting the failed to deploy errors and not seeing anything in the folder. Is this an issue where SQL 2005 is still in use?