Reporting Scenarios – More Samples

Reporting Scenarios – More Samples

  • Comments 5
  • Likes

At MMS last week I presented a session looking at various reporting scenarios based on the feedback we have received since we launched R2 last year.

The purpose of the session was to try and address the common problems and show the options available to Operations Manager users with regards to report creation.  Some of the feedback we were looking to address is highlighted below:

  •       “I need to report on how often my servers were in maintenance mode”
  •       “Why does Visual Studio seem the only option for creating the reports I need?”
  •       “Can we use operations manager for capacity planning?”
  •       “Dashboard reports that show a lot of general info…..”
  •       “How do I make reports pretty….”

We broke the session down into four main demonstrations that included samples that customers could take away and use. This blog includes those samples and instructions for using them.

Note: For those who attended the session at MMS, I stated the samples were attached to the deck but unfortunately after the deck was submitted the linked samples were removed.

Scenario 1:

       “Customer X needs to produce a report that shows the processor, memory, logical disk performance for his 100 servers and needs to see the average performance over multiple time ranges”

In this demo we showed how the Service Level Tracking feature combined with the Service Level Dashboard add-on could be used to create a self-service reporting portal.

The attached file PerformanceReporting.xml contains the sample service level rules required to create this. It also contains some additional collections rules for Disk Space targetted at the OS to make the viewing experience the same.

To use simply import the MP. This MP is targeted at Windows Server 2008 servers so to use you may need to adjust based on the servers you monitor. You may also want to adjust the service level objective goals to make them appropriate to your environment. Once imported you can go to the Service Level Dashboard and add the three service levels – Disk, Memory and Processor. This will create a portal as shown below:

Scenario 2:

       “Customer X needs to produce a report showing detailed information about how long servers spent in maintenance mode and what happened during that time”

This demo was about using other BI tools to take a query against the DW and create your own reports in a simple fashion. We used Report Builder 2.0 : http://www.microsoft.com/downloads/details.aspx?FamilyID=9f783224-9871-4eea-b1d5-f3140a253db6&displaylang=en

You can download this and take the query MaintenanceModeHistory.txt in the attached file to create something like the below:

Scenario 3:

       “Customer Y is looking for physical servers in his environment that may be suitable candidates for Virtualization, he needs a report that can show overtime the most suitable servers”

Again using the Service Level Tracking features we showed how you can create business rules(service level objectives) to drive decisions such as Virtualization Candidates and view this using the Service Level Tracking Summary Report. The VirtualizationCandidates.xml in the attached file contains the configuration to do this. Simply import the MP, adjust your service level objectives from the service level tracking node under authoring in the console and run the Service Level Tracking Summary Report.

Note: The Service Levels in this report are scoped to particular groups based on server hardware configuration. You should create your own groups based on your own hardware and link to Service Levels. The groups in the attached MP are Medium SKU Servers and Low SKU Servers and are targeted to Windows Server 2008. Once the MP is imported open the two service levels and on the scope settings page change to your own groups or reselect the two groups above:

On Import:

Change to correct group:

Scenario 4:

       “Customer X need to provide to his IT management proposed requirements for new hardware, he would like to produce a report that shows what servers in his environment may need additional SAN storage or will run out of resources in the next 6 months”

This demo is about using the data in the DW to do predictions and forecasting. The MP ForecastReport.xml in the attached file can be imported and should work without any changes. When you run the report(Reporting > Forecast Report) you will see the parameters you need to fill in. The date time ranges (To and From) are the input data from what exists in your DW and the days to forecast is how many days of prediction you need.

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included utilities are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm.

Daniel Savage

 

Attachment: MMSSamples.zip
Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
  • This is great stuff - especially the forecasting report.  A much requested feature.

    :)

  • Hi Daniel,

    I am interested in Scenario4....One I have been struggling to resolve for quite some time. So thankyou very much for posting this.

    When I import in to R2 I get the following....Is there a workaround for this problem? Thankyou,

    John Bradshaw

    =============================================

    Event Type: Error

    Event Source: Health Service Modules

    Event Category: Data Warehouse

    Event ID: 31565

    Date: 3/05/2010

    Time: 7:40:30 AM

    User: N/A

    Computer: MySCOMServer

    Description:

    Failed to deploy Data Warehouse component. The operation will be retried. Exception 'DeploymentException': Failed to perform Data Warehouse component deployment operation: Install; Component: Script, Id: '8a477b44-6d7b-fef5-beff-b328e34b7400', Management Pack Version-dependent Id: '502c3268-792c-49ac-85fa-86ebbc969ec4'; Target: Database, Server name: 'MySCOMServer', Database name: 'OperationsManagerDW'. Batch ordinal: 1; Exception: Cannot assign a default value to a local variable.

    Must declare the scalar variable "@Loop".

    Must declare the scalar variable "@LOOP".

    Incorrect syntax near the keyword 'FROM'.

    Must declare the scalar variable "@Loop".

    One or more workflows were affected by this.  

    Workflow name: Microsoft.SystemCenter.DataWarehouse.Deployment.Component

    Instance name: MySCOMServer.fqdn

    Instance ID: {3D57A144-FD0D-0B60-DC46-23448F072632}

    Management group: MyMgtGrp

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

  • This is a case sensitivity issue. I will update the MP and repost.

    Thanks for catching.

    Daniel

  • Hi Daniel, thanks for these nice reports.  I was wondering if the ForecastReport.xml has been fixed and could be reposted?  I am still getting the same error as above.

  • New post added with update attachement.