Operations Manager Report Authoring Guide

Operations Manager Report Authoring Guide

  • Comments 1
  • Likes

The report authoring guide for Operations Manager 2007 is now available for download.

http://download.microsoft.com/download/7/4/d/74deff5e-449f-4a6b-91dd-ffbc117869a2/OpsMgr2007_RprtGuide.doc

Thanks

Daniel Savage

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
  • Thanks for this tutorial. I found it useful but also found some problems with it: I tried to use it with the SCOM RTM version and found out that this guide only works with SP1 because there is no "publish" in the RTM version. After updating to SP1 it works.

    Then I followed your tutorial for "Custom Reports". You described a SQL command to create a report. I tried to use it in reporting, it didn't work. Then I tried to recreate it with the querydesigner, here's the right syntax which worked:

    SELECT     Evt.EventNumber, Evt.EventOriginId, Evt.EventPublisherRowId, Pub.EventPublisherName, Evt.DateTime, Evt.EventChannelRowId,

                         Chl.EventChannelTitle, Evt.EventCategoryRowId, Cat.EventCategoryTitle, Evt.EventLevelId, Lev.EventLevelTitle, Evt.LoggingComputerRowId,

                         Cmp.ComputerName, Evt.EventDisplayNumber, Evt.UserNameRowId, Usr.UserName, Det.RawDescription, Det.RenderedDescription,

                         Det.EventData

    FROM         Event.vEvent AS Evt INNER JOIN

                         EventPublisher AS Pub ON Evt.EventPublisherRowId = Pub.EventPublisherRowId INNER JOIN

                         EventChannel AS Chl ON Evt.EventChannelRowId = Chl.EventChannelRowId INNER JOIN

                         EventCategory AS Cat ON Evt.EventCategoryRowId = Cat.EventCategoryRowId INNER JOIN

                         EventLevel AS Lev ON Evt.EventLevelId = Lev.EventLevelId INNER JOIN

                         EventLoggingComputer AS Cmp ON Evt.LoggingComputerRowId = Cmp.EventLoggingComputerRowId INNER JOIN

                         EventUserName AS Usr ON Evt.UserNameRowId = Usr.EventUserNameRowId INNER JOIN

                         Event.vEventDetail AS Det ON Evt.EventOriginId = Det.EventOriginId

    WHERE     (Evt.EventNumber = 21025)

    The report works as it should in Visual Studio, I tried to deploy and use it with Internet Explorer, worked, too (after the test I deleted the folder and report from the report server).

    Then I followed the guide to insert the report into a ManagementPack using XML. Unfortunately it didn't work. I created a MP with SCOM and exported it and then insert the report rdl into the MP like described. I tried this link, too:

    http://blogs.msdn.com/eugenebykov/archive/2007/05/18/reports-in-management-packs.aspx

    which gives a little more detailed information about this but it either didn't work.

    What I would expect from this is, when I create a MP with a report inside that it should be deployed automatically with SCOM to the report server and that it would be shown in the list of reports. Here's where the guide has no information about the IDs and their meaning. This is described in the link above but unfortunately even if I create a description in the language tags nothing happens when I import this MP (the empty one described above was deleted before).

    I looked into the XML files from the MS-MPs which I extracted with MPtoXML powershell script and found nothing else of useful information. Here's my XML try until now (deleted most of the report definition to not make it too long):

    <?xml version="1.0" encoding="utf-8"?>

    <ManagementPack ContentReadable="true" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">

     <Manifest>

       <Identity>

         <ID>Reporting.Tests</ID>

         <Version>1.0.0.0</Version>

       </Identity>

       <Name>_Reporting Tests</Name>

       <References>

         <Reference Alias="SystemCenter">

           <ID>Microsoft.SystemCenter.Library</ID>

           <Version>6.0.6278.0</Version>

           <PublicKeyToken>31bf3856ad364e35</PublicKeyToken>

         </Reference>

       </References>

     </Manifest>

     <Presentation>

       <Folders>

         <Folder ID="Folder_832baa8989c54bf59833c1f3e753813c" Accessibility="Public" ParentFolder="SystemCenter!Microsoft.SystemCenter.Monitoring.ViewFolder.Root" />

       </Folders>

     </Presentation>

    <Reporting>

    <DataWarehouseScripts />

    <DataWarehouseDataSets />

    <ReportResources />

    <Reports>

    <Report ID="Reporting.Tests.Event21025" Accessibility ="Public" Visible="true">

    <Definition>

    <Report xmlns="http://schemas.microsoft.com/sqlserver/reporting/2005/01/reportdefinition" xmlns:rd="http://schemas.microsoft.com/SQLServer/reporting/reportdesigner">

    <DataSources>

    <DataSource Name="SCOMDataSourceReportingTests">

    .

    .

    .

    .

    </DataSets>

    </Report>

    </Definition>

    </Report>

    </Reports>

    </Reporting>

     <LanguagePacks>

       <LanguagePack ID="DEU" IsDefault="false">

         <DisplayStrings>

           <DisplayString ElementID="Reporting.Tests">

             <Name>_Reporting Tests</Name>

             <Description>Zum Testen von eigenen Reportings mit SCOM</Description>

           </DisplayString>

     <DisplayString ElementID="Reporting.Tests.Event21025">

     <Name>_Reporting Tests</Name>

     <Description>Zum Testen von eigenen Reportings mit SCOM</Description>

     </DisplayString>

     <DisplayString ElementID="Folder_832baa8989c54bf59833c1f3e753813c">

             <Name>_Reporting Tests</Name>

           </DisplayString>

         </DisplayStrings>

       </LanguagePack>

       <LanguagePack ID="ENU" IsDefault="false">

         <DisplayStrings>

           <DisplayString ElementID="Reporting.Tests">

             <Name>_Reporting Tests</Name>

             <Description>Zum Testen von eigenen Reportings mit SCOM</Description>

           </DisplayString>

     <DisplayString ElementID="Reporting.Tests.Event21025">

     <Name>_Reporting Tests</Name>

     <Description>Zum Testen von eigenen Reportings mit SCOM</Description>

     </DisplayString>

     <DisplayString ElementID="Folder_832baa8989c54bf59833c1f3e753813c">

             <Name>_Reporting Tests</Name>

           </DisplayString>

         </DisplayStrings>

       </LanguagePack>

     </LanguagePacks>

    </ManagementPack>

    It imports perfectly, no error message. Only thing is that I can't see any new report in the report list. Maybe you should expand the guide to explain a little bit more detailed what must be inserted here so that SCOM created a folder name in the reporting service and deploy it and where are the definitions of the folder name and report name?

    Thanks in advance

    Christian