Reports in System Center Operations Manager 2007 analyze information stored in the data warehouse. In comparison, data included in views comes from the Operations Manager database. The data warehouse includes aggregated data over much longer periods of time.
Linked reports can be created using the Authoring console to provide customized versions of generic reports that are included with Operations Manager 2007. The following sections provide details of linked reports and processes for creating and including them in your management pack.
In addition to this guide, a video titled How Do I: Create a Linked Report in Operations Manager 2007? is available that provides an overview of linked reports including a walkthrough of creating two sample reports.
Each linked report is defined by the properties listed in the following table. The process of designing and creating a linked report primarily involves setting and modifying these properties.
Base Report
Each linked report has a report that it is based on. The base report defines the contents and formatting of the report. It has a set of parameters that the linked report must provide values for.
Any report can be a base report for a linked report. The generic reports are specifically designed for this purpose. They are the focus of this documentation.
Target Class
A linked report can have a target class although one is not required. If a target class is defined, the linked report is listed in the Actions pane of the Operations console when one or more instances of the target class are selected. If you select the report from the Actions pane, the selected instances are included in the Object XML Picker control of the report. If the report does not have a target class, it can only be run from the Reporting pane.
Parameter Block and Parameters
Most reports have parameters that each require a value for the report to run. The linked report is required to provide a value for each of the parameters required by its base report. These values can either be included with the linked report or the user provides them when running or scheduling the linked report.
Values that should be hardcoded by the linked report without requiring the user to provide them are included in parameters. Those values that the user should be able to select are defined by the linked report in parameter blocks. Each report’s parameter block defines one or more controls that the user sees when the report opens. Each control provides the value for one or more parameters based on input from the user.
Most reports have parameters that require values when the report is run to provide details of what content the report should contain and how it should be configured. Linked reports must provide a value for each parameter required by its base report. These values can be provided either through controls that enable the user to provide the value when the user runs the report or by having the linked report provide a specific value.
Each report has its own set of parameters depending on its specific requirements. In addition to parameters unique to a particular report, multiple generic reports share a common set of parameters. This section provides details of these common parameters. The sections for each type of report in the Generic Reports section provide details about other parameters that are unique to specific reports.
The following parameters are common to different kinds of reports.
Most of the generic reports require a date range that provides the start date and end date for the data to include in the report. Generic reports use a set of common parameters to define these dates. Rather than just enabling a specific start date and end date, parameters can define dates relative to the current date. Therefore, a linked report can specify a predetermined date range without requiring input from the user when the report is run.
For example, you can create a linked report that shows data from the previous week. The starting date could be set to the seven days prior to the date that the report is run, or it could be set to the Sunday of the previous week. Each time you run the report, the dates are set dynamically so that you do not have to provide the start and end date each time.
The following table lists the date and time parameters and their allowed values.
TimeZone
Code for the time zone of the provided dates.
If the Relative Date Time Picker control is not used to let the user select the time zone, the value should be left blank to use the time zone of the current workstation.
A valid time zone code such as E001000000000000C4FFFFFF00000B 00000001000200000000000000000 00300000002000200000000000000 |Pacific Standard Time
TimeZoneName
The name of the time zone.
A valid time zone name such as (UTC-08:00) Pacific Time (US & Canada)
StartDate_BaseType
EndDate_BaseType
The type of date for the start date or the end date.
StartDate_BaseValue
EndDate_BaseValue
Date and time. Date is only used when StartDate_BaseType is Fixed. For other values of StartDate_BaseType only the time portion of the value is used.
A valid data and time string such as 1/1/2010 12:00:00 AM
StartDate_OffsetType
EndDate_OffsetType
The type of offset to use from the base date and value
A valid integer such as -7.
The following table shows example values required for the relative date parameters to achieve different scenarios.
Specific date and time
Fixed
5/17/2010 02:00:00 PM
None
0
The current date at a specific time
Today
1/1/2010 12:00:00 AM
Yesterday at a specific time
1/1/2010 02:00:00 PM
Day
-1
This week
Sunday
Previous week
Week
This month
FirstDayMonth LastDayMonth
Previous month
Month
This quarter
FirstDayQuarter LastDayQuarter
Time only
Previous quarter
Quarter
This year
FirstDayYear LastDayYear
Previous year
Year
Some reports use parameters in addition to the relative data time parameters that restrict the analysis period to business hours. These parameters are listed in the following table.
TimeType
Specifies if all hours should be used or business hours only.
Regular Business
TimeWeekMap
Specifies the days of the week that business hours are applied. One or more values may be provided.
Only applies if the TimeType is Business.
Sunday Monday Tuesday Wednesday Thursday Friday Saturday
If the TimeType parameter is set to Business, the time in the StartDate_BaseValue and EndDate_BaseValue parameter is used to define business hours. The date portion of those values is used to define the start date and end date.
The ManagementGroupID parameter specifies the GUID of the management group to retrieve data from.
You can use the Microsoft.SystemCenter.DataWarehouse.Report.ParameterPrompt.ManagementPack prompt with the Checked List Box or Combo Box control to populate the control with the list of management packs installed in the management group.
The ManagementPackID parameter specifies the ID for one or more management packs to include in the report.
The ObjectList parameter contains XML code defining the objects used in the report. This includes an element called Object that includes the ID for the object in the data warehouse. This ID is typically not known when the report is created and is provided by the user with the Performance Object Picker control when the report is run. More than one Object element can be used if the series should contain data from more than one target object.
The Object element includes an attribute called Use that defines whether the object itself is used in the report or whether the object and all its contained objects are used. The value of this attribute can be either Self or Containment.
The following XML code shows an example of the ObjectList parameter including two objects.
<
Data
>
Objects
Object
Use
=
"Containment"
>5</
"Self"
>2</
</
Performance reports also use the ObjectList parameter, but it includes additional elements in those reports. This is documented in Performance Parameters.
The following parameters are used in alert reports to refer to the properties of an alert.
The Severity parameter specifies the severity level of an alert using a value from the following table.
Information
1
Warning
2
Critical
Use the prompt Microsoft.SystemCenter.DataWarehouse.Report.ParameterPrompt.AlertSeverity to populate a Checked List Box or Combo Box control with the different severity values and their friendly names.
The Priority parameter specifies the priority level of an alert using a value from the following table.
Low
Medium
High
Use the prompt Microsoft.SystemCenter.DataWarehouse.Report.ParameterPrompt.AlertPriority to populate a Checked List Box or Combo Box control with the different severity values and their friendly names.
The following parameters are used in Event reports to refer to the properties of an event.
The EventChannel parameter is a string specifying the channel of an alert. For a Windows event, this is the name of the event log.
Use the prompt Microsoft.SystemCenter.DataWarehouse.Report.ParameterPrompt.EvenChannel to populate a Checked List Box or Combo Box control with the list of event channels currently in the data warehouse.
The EventSource parameter is a string specifying the source of an alert. For a Windows event, this is the publisher name. Use the prompt Microsoft.SystemCenter.DataWarehouse.Report.ParameterPrompt.EventSource to populate a Checked List Box or Combo Box control with the list of event sources currently in the data warehouse.
The EventType parameter is a string with the name of the level of severity of the event. This value can typically be left blank to indicate that all event types should be included in the report. The following strings indicate the severity:
Use the prompt Microsoft.SystemCenter.DataWarehouse.Report.ParameterPrompt.EventType to populate a Checked List Box or Combo Box control with the list of event types currently in the data warehouse.
The EventCategory parameter specifies the category of the event.
Use the prompt Microsoft.SystemCenter.DataWarehouse.Report.ParameterPrompt.EventCategory to populate a Checked List Box or Combo Box control with the list of event categories currently in the data warehouse.
The following parameters are used in Performance reports in Operations Manager 2007 to set the contents and configuration of performance charts.
The AggregationType parameter specifies how to aggregate the data on the X-axis of the performance chart. Allowed values for this parameter are provided in the following table.
Daily
Weekly
3
Monthly
4
Yearly
Use the Microsoft.SystemCenter.DataWarehouse.Report.ParameterPrompt.Histogram prompt to populate a ComboBox control with the possible values for the AggregationType parameter.
The DataAggregation parameter specifies how to aggregate the data included in the performance chart. Allowed values for this parameter are provided in the following table.
Hourly
Use the prompt Microsoft.SystemCenter.DataWarehouse.Report.Library!Microsoft.SystemCenter.DataWarehouse.Report.ParameterPrompt.DataAggregation to populate a Combo Box control with the list of sources currently in the data warehouse.
The Enable3D parameter specifies whether the chart should be displayed in 3D or not. It can have a value of True or False.
Use the Microsoft.SystemCenter.DataWarehouse.Report.ParameterPrompt.Chart3D prompt to populate a Boolean Picker control with the valid values for the Enable3D parameter.
In performance reports, the ObjectList parameter contains XML code defining the configuration of the charts and series included in the report. The following table describes the elements that may be included in this parameter.
ID for the object in the data warehouse. This ID is typically not known and is provided by the user who has the Performance Object Picker control.
More than one Object element can be used if the series should contain data from more than one target object.
The element includes an attribute called Use that defines whether the object is used or whether the object and all its contained objects are used.
The ID of an object in the data warehouse.
The Use attribute may have the value Self or Containment.
Rule
The rule that collects the data to include in the series. This should be an $MPElement variable instead of a GUID to allow for it to be transferred between management packs.
The GUID of the rule. If the parameter is populated from a control when the report is run, it will be the actual GUID of the rule. If a value is provided in the linked report, an $MPElement variable is typically used such as $MPElement[Name="MyMP.MyApp.MyCollectionRule"]$.
Scale
Multiplier to use against the value.
An integer value. For example, to use the collected value, you would set this parameter to 1. To multiply the collected value by 100, you would set this parameter to 100. To divide the collected value by 1,000, you would set this parameter to .001.
Type
The kind of graph
One of the following values
Color
Three numeric values that indicate the color of the line.
The allowed values are shown in the following table.
The values for common values for the Color element are listed in the following table.
Light Blue
63,63,255
Dark Green
0,159,0
Light Red
255,31,31
Yellow
255,221,0
Black
0,0,0
Dark Blue
31,31,159
Light Green
63,255,63
Orange
255,127,63
Light Gray-Blue
191,191,255
Brown
191,111,47
Each chart is defined by a Values element and each series in the chart is defined by a Value element. The following XML code shows an example of a report that has two charts. The first chart has two series, and the second chart has a single series.
Values
Value
>$MPElement[Name="MyMP.MyApp.MyCollectionRule1"]$</
>63,63,255</
>Line</
>1</
>$MPElement[Name="MyMP.MyApp.MyCollectionRule2"]$</
>0,159,0</
>.01</
>$MPElement[Name="MyMP.MyApp.MyCollectionRule3"]$</
>255,127,63</
>100</
The RuleId parameter specifies the ID of a collection rule for performance reports that display the top objects or instances for a particular rule. If this parameter is collected by a control when you run the report, this is the actual GUID of the rule. If a specific rule is specified in the linked report, an $MPElement variable for the rule should be used.
Use the Microsoft.SystemCenter.DataWarehouse.Report.Library!Microsoft.SystemCenter.DataWarehouse.Report.ParameterPrompt.PerformanceRule prompt to populate a Performance Rule Picker or Performance Rule Instance Picker control with a list of rule IDs currently in the data warehouse.
The RuleInstance parameter specifies the name of one or more instances to include in a performance object report.
The SortOrder parameter specifies whether to sort from the top or bottom in a top instances or top object performance report. Allowed values for this parameter are provided in the following table.
Top
Bottom
Use the prompt Microsoft.SystemCenter.DataWarehouse.Report.Library!Microsoft.SystemCenter.DataWarehouse.Report.ParameterPrompt.TopAlgorithmParameter to populate a Combo Box control with the allowed values for the SortOrder parameter.
The TopCount parameter specifies how many instances or objects to include in a performance report.
Use the prompt Microsoft.SystemCenter.DataWarehouse.Report.Library!Microsoft.SystemCenter.DataWarehouse.Report.ParameterPrompt.TopAlgorithm to populate a Combo Box control with the allowed values for the TopCount parameter.
Report controls are displayed in the Operations console when you open a report. They allow you to set the values of parameters for the report before running it. When you want to create a linked report and you are not going to provide specific values for certain parameters, you typically use the same control as the base report for the same parameter. You can also provide configuration for certain controls to modify their behavior.
Controls are displayed in the header of the report when it is opened in the Operations console. The width of the header expands to fit the width of the report window. The parameter block of the report has a columns attribute that defines how many columns the header should be separated into. Each control has a columnSpan attribute that defines the width of the control. If the columnSpan attribute is not provided, it is set to the default value of 1.
The controls are populated into the header from left to right in the order that they are listed in the parameter block. When the column width of the header has been reached, the controls continue to populate from the left side of the header beneath the control in the same horizontal position.
The height of the control is defined by the rowSpan attribute. If the rowSpan attribute is not provided, it is set to the default value of 1. If a control has a rowSpan that is greater than the rowSpan of other controls, the controls stack on top of each other before they are placed in the next column.
For example, the following table lists the controls with their columnSpan and rowSpan attributes for the Alert report. The Relative Date Time Picker and the Monitoring Object XML Picker controls are side-by-side and take up the entire height of the header. Two Checked List Box controls are on the right side of the header and sit on top of each other.
The columns attribute of the parameter block is set to 6. Because the columnSpan attribute for Relative Date Time Picker and Monitoring Object XML Picker are set to 2 and 3 respectively, these controls take up the first five column positions of the header. The Checked List Box controls have a columnSpan of 1 meaning that they should each take up an additional column position. Because the rowSpan for both is 1, and the rowSpan for the first two controls is 2, the controls are able to stack on top of each other and take up just a single column position. If the rowSpan for these controls were the same as the first two controls, the second Checked List Box would wrap to the next position in the first column.
Microsoft.SystemCenter.DataWarehouse.Report.ParameterControl.RelativeDateTimePicker
Microsoft.SystemCenter.DataWarehouse.Report.ParameterControl.MonitoringObjectXmlPicker
Microsoft.SystemCenter.DataWarehouse.Report.ParameterControl.CheckedListBox
Each control has one or more report parameters that it collects data for. This parameter is specified in the binding attribute for the control. If a control uses a prompt, it does not require a binding attribute because the prompt maps to a specific parameter.
Prompts can be used to populate a control with possible values. For example, Event reports use a parameter for the event source. The prompt Microsoft.SystemCenter.DataWarehouse.Report.ParameterPrompt.EventSource retrieves a list of all sources in the data warehouse for populating a check box or combo box. Appropriate prompts for different controls and parameters are included in the definition of the generic report. You can copy it to the linked report as part of the parameter block.
Prompts that can be used for different parameters are defined with the parameter in Report Parameters.
Properties can be used to control the configuration of certain controls. For example, the Numeric Up Down control allows for two parameters called Minimum and Maximum that define the range of allowed values.
Properties that can be used with different controls are defined with the controls in the following sections. They can be used with multiple types of reports.
The following sections provide details for each generic report. These are organized into sections that include reports returning similar data. Provided for each report are the list of the parameters and controls of the report and the XML code of its parameter block. You can copy this XML code into the parameter block of a linked report based on the generic report. As described in Building a Linked Report, copying the parameter block from the base report to the linked report is one step in creating the linked report.
The following table lists the generic reports that can be used as a base for linked reports.
Alert Reports
Alerts
Shows for selected objects alerts raised during the selected report duration and for given filter parameters.
Alert Logging Latency
Helps to isolate issues in monitoring with System Center Operations Manager by showing the logging latency of an alert for selected objects over time.
Most Common Alerts
Shows for selected objects the most common alerts raised during the selected report duration and for given filter parameters.
Event Reports
Custom Event
Shows event data filtered by all selected parameters.
Event Analysis
Shows a table of events and a count by server filtered by all entered parameters.
Most Common Events
Shows for selected objects the most common events raised during the selected report duration and for given filter parameters.
Performance Reports
Performance
Shows selected objects and performance counter values graphically over time.
Performance Details
Shows selected objects and performance counter values graphically over time with fixed parameters.
Performance Top Instances
Shows for selected objects and a specific performance counter rule the top or bottom "n" instances.
Performance Top Objects
Shows for a specific performance counter rule the top or bottom "n" objects.
Availability Reports
Availability
Shows for selected objects the time in state during the selected report duration. Time in state is summarized by default as per the objects availability Monitors.
Configuration Reports
Configuration Changes
Shows for selected objects the changes in configuration over time.
Custom Configuration
Shows configuration data filtered by all entered parameters.
Alert reports in Operations Manager 2007 access alerts that have been created from rules or monitors. Following is a description of each Alert generic report that includes a description of its report controls and report parameters. The parameter block of each report that can be copied into the definition of a linked report is also included.
The Alerts report shows all raised alerts for a given set of objects during the specified time period. You can add additional filters for alert severity and priority to scope report output.
The ID of the Alerts report is Microsoft.SystemCenter.DataWarehouse.Report.Alert.
The controls that are used in the Alerts report are shown in the following table with the parameters that each populates.
Relative Data Time Picker
StartDate_BaseType StartDate_BaseValue StartDate_OffsetType StartDate_OffsetValue EndDate_BaseType EndDate_BaseValue EndDate_OffsetType EndDate_OffsetValue TimeZone TimeZoneName
All alerts that were raised in the date and time range that are included in the report. These are the standard date parameters described in Common Parameters.
This control can be removed if a defined relative data time range is provided for the parameter.
Monitoring Object XML Picker
ObjectList ManagementGroupId
Specifies the groups or objects that are included in the report. This includes an ID from the data warehouse so that the parameters cannot be populated without the control. This is the standard Object XML Picker control described in Common Report Controls.
This control should not be removed from the report.
Checked List Box
Severity
Specifies one or more alert severity values to include in the report. The values for this parameter are provided in Alert Parameters.
This control can be removed from the report if one or more specific severity values are provided for the parameter.
Priority
Specifies one or more alert priority values to include in the report. The values for this parameter are provided in Alert Parameters.
This control can be removed from the report if one or more specific priority values are provided for the parameter.
The following is the parameter block for the Alerts report. You can copy it into a linked report based on the Alerts report to replicate the controls of the base report.
ParameterBlock
columns
"6"
xmlns
"http://schemas.microsoft.com/mom/reporting/2007/ReportParameterSettings"
Controls
Control
type
"Microsoft.SystemCenter.DataWarehouse.Report.ParameterControl.RelativeDateTimePicker"
rowSpan
"2"
columnSpan
ReportParameters
ReportParameter
name
"TimeZone"
binding
Prompt
>Microsoft.SystemCenter.DataWarehouse.Report.Library!Microsoft.SystemCenter.DataWarehouse.Report.ParameterPrompt.TimeZone</
"TimeZoneName"
/>
"StartDate_BaseType"
"StartDate_BaseValue"
>Microsoft.SystemCenter.DataWarehouse.Report.Library!Microsoft.SystemCenter.DataWarehouse.Report.ParameterPrompt.StartDateTime</
"StartDate_OffsetType"
"StartDate_OffsetValue"
"EndDate_BaseType"
"EndDate_BaseValue"
>Microsoft.SystemCenter.DataWarehouse.Report.Library!Microsoft.SystemCenter.DataWarehouse.Report.ParameterPrompt.EndDateTime</
"EndDate_OffsetType"
"EndDate_OffsetValue"
"Microsoft.SystemCenter.DataWarehouse.Report.ParameterControl.MonitoringObjectXmlPicker"
"3"
"ObjectList"
>Microsoft.SystemCenter.DataWarehouse.Report.Library!Microsoft.SystemCenter.DataWarehouse.Report.ParameterPrompt.ObjectList</
"ManagementGroupId"
"GroupList"
"Microsoft.SystemCenter.DataWarehouse.Report.ParameterControl.CheckedListBox"
"1"
"Severity"
>Microsoft.SystemCenter.DataWarehouse.Report.Library!Microsoft.SystemCenter.DataWarehouse.Report.ParameterPrompt.AlertSeverity</
"Priority"
>Microsoft.SystemCenter.DataWarehouse.Report.Library!Microsoft.SystemCenter.DataWarehouse.Report.ParameterPrompt.AlertPriority</
The Alert Logging Latency report shows the time an alert takes from being picked up on the agent to the time it is written to the database. Every alert written to the database is time-stamped. The time the alert was raised on the agent is subtracted to give you the latency. This report allows for comparing the reported latencies against a threshold, which can be entered as a parameter.
The ID of the Alert Logging Latency report is Microsoft.SystemCenter.DataWarehouse.Report.AlertLoggingLatency.
The controls that are used in the Alert Logging Latency report are shown in the following table with the parameters that each populates.
Specifies all alerts that were raised in the date and time range included in the report. These are the standard date parameters described in Common Parameters.
ObjectList ManagementGroupkId
Combo Box
Threshold
Specifies a single value, defining the threshold for the alert latency. Alerts are separated in the report between those above the threshold and those below the threshold. This value is a duration measured in seconds. The valid values are listed in the table below.
AggregationType
Specifies a single value, defining the aggregation type to use for the graph. The allowed values are listed in the table below.
The following table lists the valid values for the threshold parameter.
1 second
2 seconds
5
5 seconds
10
10 seconds
15
15 seconds
30
30 seconds
60
1 minute
120
2 minutes
300
5 minutes
600
10 minutes
900
15 minutes
1800
30 minutes
The following table lists the valid values for the AggregationType parameter.
The following is the parameter block for the Alert Logging Latency report. You can copy it into a linked report based on the Alert Logging Latency report to replicate the controls of the base report.
"5"
"4"
"Microsoft.SystemCenter.DataWarehouse.Report.ParameterControl.ComboBox"
"Threshold"
>Microsoft.SystemCenter.DataWarehouse.Report.Library!Microsoft.SystemCenter.DataWarehouse.Report.ParameterPrompt.Threshold</
"AggregationType"
>Microsoft.SystemCenter.DataWarehouse.Report.Library!Microsoft.SystemCenter.DataWarehouse.Report.ParameterPrompt.Aggregation</
The Most Common Alerts report helps identify high-volume alerts, the management pack they originate from, the volume a distinct alert contributes to the total number of alerts, and the resolution times. This report helps tune alerts.
The ID of the Most Common Alerts report is Microsoft.SystemCenter.DataWarehouse.Report.MostCommonAlerts.
The controls that are used in the Most Common Alerts report are shown in the following table with the parameters that each populates.
All alerts that were raised in the date and time range are included in the report. These are the standard date parameters described in Common Parameters.
ManagementPackId
Specifies one or more management packs containing the rules and monitors creating the alerts to include in the report.
Numeric Up Down
AlertThreshold
Specifies the number of alerts to include in the report. This is any numeric value between 1 and 100.
The following is the parameter block for the Most Common Alerts report. You can copy it into a linked report based on the Most Common Alerts report to replicate the controls of the base report.
"ManagementPackId"
>Microsoft.SystemCenter.DataWarehouse.Report.Library!Microsoft.SystemCenter.DataWarehouse.Report.ParameterPrompt.ManagementPack</
"Microsoft.SystemCenter.DataWarehouse.Report.ParameterControl.NumericUpDown"
"AlertThreshold"
>Microsoft.SystemCenter.DataWarehouse.Report.Library!Microsoft.SystemCenter.DataWarehouse.Report.ParameterPrompt.TopAlgorithmParameter</
Properties
Property
"Minimum"
"Maximum"
Event reports in Operations Manager 2007 access events that are collected by rules. Following is a description of each Event generic report that includes a description of its report controls and report parameters. The parameter block of each report that can be copied into the definition of a linked report is also included.
This report shows a table of events and a count by server filtered by all entered parameters.
The ID of the Event Analysis report is Microsoft.SystemCenter.DataWarehouse.Report.EventAnalysis.
The controls that are used in the Event Analysis report are shown in the following table with the parameters that each populates.
Relative Date Time Picker
All events that were created in the date and time range are included in the report. These are the standard date parameters described in Common Parameters.
Event Source
Specifies the event source. The valid values are described in Event Parameters. Leave blank for all.
This control can be removed from the report if one or more specific event source values are provided for the parameter.
Event Type
Specifies the event type. The valid values are described in Event Parameters. Leave blank for all.
This control can be removed from the report if one or more specific event type values are provided for the parameter.
Event Category
Specifies the event category. The valid values are described in Event Parameters. Leave blank for all.
This control can be removed from the report if one or more specific event category values are provided for the parameter.
Event ID
Specifies the event ID. Leave blank for all.
This control can be removed from the report if one or more specific event ID values are provided for the parameter.
The following is the parameter block for the Event Analysis report. You can copy it into a linked report based on the Event Analysis report to replicate the controls of the base report.
"EventSource"
>Microsoft.SystemCenter.DataWarehouse.Report.Library!Microsoft.SystemCenter.DataWarehouse.Report.ParameterPrompt.EventSource</
"EventSourceLookup"
"Lookup"
"EventType"
>Microsoft.SystemCenter.DataWarehouse.Report.Library!Microsoft.SystemCenter.DataWarehouse.Report.ParameterPrompt.EventType</
"EventCategory"
>Microsoft.SystemCenter.DataWarehouse.Report.Library!Microsoft.SystemCenter.DataWarehouse.Report.ParameterPrompt.EventCategory</
"EventID"
>Microsoft.SystemCenter.DataWarehouse.Report.Library!Microsoft.SystemCenter.DataWarehouse.Report.ParameterPrompt.EventID</
The Custom Event report includes collected events containing specific information. The list of event details is defined by the rules collecting the events. By selecting the check box, you can select to print a detail of the event on the report. The controls to the right allow for defining the order of the selected items from left (higher in the parameter list) to right (lower in the parameter list).
The ID of the Custom Event report is Microsoft.SystemCenter.DataWarehouse.Report.EventTemplate.
The controls that are used in the Custom Event report are shown in the following table with the parameters that each populates.
Object Picker
Report Column Picker
Columns
Specifies the columns to be included in the output of the report and the columns that are used to filter the returned data. This is described in more detail later in this section.
This control can be removed if a set of column definitions is provided for this parameter.
The Columns parameter defines the columns to include in the output of the report and the columns that are used to filter the output. The table below lists the values that are required to define each column:
ID Element
Element that defines the ID of the property. If the Operations console is used, this will be the GUID of the property. This must be changed to an $MPElement variable so that the management pack can be transferred between management groups.
Visible Attribute
Attribute with a value of True or False specifying whether the column should be displayed. If the value is False, it is expected that the column is only used to filter the output.
Filter Element
If used, this element identifies the column as being used for filtering the output. The Type attribute can be either Contains or Equals, and the content of the element includes the text to match.
If the column should only be displayed and not used for filtering, the filter element is not included.
All properties are included as a single parameter entry using the syntax shown in the following example. This example shows a report that uses the following details:
Column
Visible
"False"
ID
>EventLevelTitle</
Filter
"Equals"
>Error</
"True"
>EventDisplayNumber</
>DateTime</
>EventPublisherName</
"Contains"
>Health Service</
The following is the parameter block for the Custom Event report. You can copy it into a linked report based on the Custom Event report to replicate the controls of the base report.
"7"
"Microsoft.SystemCenter.DataWarehouse.Report.ParameterControl.ReportColumnPicker"
"Columns"
"ColumnList"
The Most Common Events report helps identify high-volume events, the agent they originated from, and the volume that a distinct event contributes to the total number of events. This report helps tune events.
The ID of the Most Common Events report is Microsoft.SystemCenter.DataWarehouse.Report.MostCommonEvents.
The controls that are used in the Most Common Events report are shown in the following table with the parameters that each populates.
EventChannel
Specifies ene or more values indicating the event channel.
EventSource
Specifies one or more values for the event source. The valid values are described in Event Parameters.
EventType
Specifies one or more values for the event type. The valid values are described in Event Parameters. Leave blank for all.
EventThreshold
Specifies the number of events to include in the report. This is any numeric value between 1 and 100.
The following is the parameter block for the Most Common Events report. You can copy it into a linked report based on the Most Common Events report to replicate the controls of the base report.
"8"
"EventChannel"
>Microsoft.SystemCenter.DataWarehouse.Report.Library!Microsoft.SystemCenter.DataWarehouse.Report.ParameterPrompt.EventChannel</
"EventThreshold"
Performance reports in Operations Manager 2007 analyze performance data that collected by rules. Following is a description of each Performance generic report that includes a description of its report controls and report parameters. The parameter block of each report that can be copied into the definition of a linked report is also included.
The Performance report shows one or multiple charts and display data as historical chart or histograms. For the selected time range, the report includes performance data with charts and a data tables.
The ID of the Performance report is Microsoft.SystemCenter.DataWarehouse.Report.Performance.
The controls that are used in the Performance report are shown in the following table with the parameters that each populates.
Business Relative Date Time Picker
StartDate_BaseType StartDate_BaseValue StartDate_OffsetType StartDate_OffsetValue EndDate_BaseType EndDate_BaseValue EndDate_OffsetType EndDate_OffsetValue TimeZone TimeZoneName TimeType TimeWeekMap
Only performance data that was collected in the date and time range are included in the report. These are the standard date parameters described in Common Parameters.
Performance Object Picker
Specifies objects that are included in the report and the contents and configuration of the graph. This is the standard Performance Object Picker control described in Performance Report Controls.
This control is typically replaced by Linked Performance Object Picker in linked reports that use the contents and configuration of the graph provided in the properties for that control.
DataAggregation
Specifies how to aggregate the data included in the report. Allowed values for this parameter are provided in Performance Parameters.
This control can be removed from the report if you provide a specific value for the DataAggregation parameter.
Single value that specifies how to aggregate the data on the X-axis. Allowed values for this parameter are provided in Performance Parameters.
This control can be removed from the report if you provide a specific value for the AggregationType parameter.
Boolean Picker
Enable3D
A value of true or false indicates whether the graph should be displayed in 3D.
This control can be removed from the report if you provide a specific value for the Enable3D parameter.
The following is the parameter block for the Performance report. You can copy this into a linked report that is based on the Performance report to replicate the controls of the base report.
"DataAggregation"
>Microsoft.SystemCenter.DataWarehouse.Report.Library!Microsoft.SystemCenter.DataWarehouse.Report.ParameterPrompt.DataAggregation</
"Microsoft.SystemCenter.DataWarehouse.Report.ParameterControl.PerformanceChartObjectPicker"
"Microsoft.SystemCenter.DataWarehouse.Report.ParameterControl.BusinessRelativeDateTimePicker"
"TimeType"
"TimeWeekMap"
>Microsoft.SystemCenter.DataWarehouse.Report.Library!Microsoft.SystemCenter.DataWarehouse.Report.ParameterPrompt.Histogram</
"Microsoft.SystemCenter.DataWarehouse.Report.ParameterControl.BooleanPicker"
"Enable3D"
>Microsoft.SystemCenter.DataWarehouse.Report.Library!Microsoft.SystemCenter.DataWarehouse.Report.ParameterPrompt.Chart3D</
The Performance Detail report shows a series with these fixed settings:
If a Histogram is specified, this report displays a link to a table detailing average, min, max and standard deviation for all time periods averaged into one x-axis unit. A second, smaller chart details the number of performance counter samples making up this report.
The ID of the Performance Detail report is Microsoft.SystemCenter.DataWarehouse.Report.PerformanceDetail.
The controls that are used in the Performance Detail report are shown in the following table with the parameters that each populates.
This control is typically replaced by Linked Performance Object Picker in linked reports that use the contents and configuration of the graph provided in that control’s properties.
The following is the parameter block for the Performance Detail report. You can copy this into a linked report based on the Performance Detail report to replicate the controls of the base report.
"Microsoft.SystemCenter.DataWarehouse.Report.ParameterControl.PerformanceObjectPicker"
The Performance Top Instances report shows columns for every found object starting at 0 to the max or min value for the selected reporting time range. The chart also indicates with a black error bar the fluctuation in value of this object for the selected reporting time range. If the error bar is very small this object was for the reporting time range always close to value displayed by the column. If it is very wide the object fluctuates and the top or bottom value should be not taken as the value which is to be expected.
The ID of the Performance Top Instances report is Microsoft.SystemCenter.DataWarehouse.Report.PerformanceTopInstance.
The controls that are used in the Performance Top Instances report are shown in the following table with the parameters that each populates.
Monitoring Object Picker
SortOrder
Single value that specifies whether to sort the instances from the top or bottom. Allowed values for this parameter are provided in Performance Parameters.
This control can be removed from the report if you provide a specific value for the SortOrder parameter.
TopCount
Integer specifying the number of instances to include in the report. Allowed values for this parameter are provided in Performance Parameters.
This control can be removed from the report if you provide a specific value for the TopCount parameter.
Performance Rule Picker
RuleId ManagementGroupId
Single GUID or $MPElement variable specifying the rule collecting the performance counter. The RuleId is discussed in Performance Parameters.
This control can be removed from the report if you provide a specific value for the RuleId parameter.
The following is the parameter block for the Performance Top Instances report. You can copy the code block into a linked report based on the Performance Top Instances report to replicate the controls of the base report.
"SortOrder"
>Microsoft.SystemCenter.DataWarehouse.Report.Library!Microsoft.SystemCenter.DataWarehouse.Report.ParameterPrompt.TopAlgorithm</
"TopCount"
"Microsoft.SystemCenter.DataWarehouse.Report.ParameterControl.PerformanceRulePicker"
"RuleId"
>Microsoft.SystemCenter.DataWarehouse.Report.Library!Microsoft.SystemCenter.DataWarehouse.Report.ParameterPrompt.PerformanceRule</
The Performance Top Objects report shows columns for every found object starting at 0 to the max or min value for the selected reporting time range. The chart also indicates with a black error bar the fluctuation in value of this object for the selected reporting time range. If the error bar is very small this object was for the reporting time range always close to value displayed by the column. If it is very wide the object fluctuates and the top or bottom value should be not taken as the value which is to be expected.
The ID of the Performance Top Objects report is Microsoft.SystemCenter.DataWarehouse.Report.PerformanceTop.
The controls that are used in the Performance Top Objects report are shown in the following table with the parameters that each populates.
Performance Rule Instance Picker
RuleId ManagementGroupId RuleInstance
This control can be removed from the report if you provide a specific value for the RuleId and RuleInstance parameters.
ManagementGroupID
Single value that specifies the GUID of the management group to retrieve the data from.
Single value that specifies whether to sort the objects from the top or bottom. Allowed values for this parameter are provided in Performance Parameters.
Integer specifying the number of objects to include in the report. Allowed values for this parameter are provided in Performance Parameters.
The following is the parameter block for the Performance Top Objects report. You can copy this into a linked report based on the Performance Top Objects report to replicate the controls of the base report.
>Microsoft.SystemCenter.DataWarehouse.Report.Library!Microsoft.SystemCenter.DataWarehouse.Report.ParameterPrompt.ManagementGroup</
"Microsoft.SystemCenter.DataWarehouse.Report.ParameterControl.PerformanceRuleInstancePicker"
"RuleInstance"
"InstanceList"
Availability reports in Operations Manager 2007 provide an analysis of the availability of monitored objects. Following is a description of each Availability generic report that includes a description of its report controls and report parameters. The parameter block of each report that can be copied into the definition of a linked report is also included.
For every managed object within System Center Operations Manager, monitors configured in each of the disciplines below determine an objects time in state and then roll-up to an objects overall health. The availability Availability report by default shows an objects time in state as per the monitors that roll-up within the availability Availability discipline.
The controls that are used in the Availability report are shown in the following table with the parameters that each populates.
Only availability of the included objects in the date and time range is included in the report. These are the standard date parameters described in Common Parameters.
Downtime
Specifies one or more values defining what states should be considered as downtime. The valid values for this parameter are provided in the following table.
Specifies the type of aggregation that should be performed on the data using a value from the following table.
The DownTime parameter can accept one of the values from the following table:
Unmonitored
Monitor disabled
Unplanned Maintenance
6
Planned Maintenance
7
Monitoring Unavailable
The DownTime parameter can use the prompt Microsoft.SystemCenter.DataWarehouse.Report.Library!Microsoft.SystemCenter.DataWarehouse.Report.ParameterPrompt.AvailabilityDownTime in a Combo Box control to list the valid values.
The DataAggregation parameter can accept one of the values from the following table:
The DataAggregation parameter can use the prompt Microsoft.SystemCenter.DataWarehouse.Report.ParameterPrompt.DataAggregation in a Combo Box control to list the valid values.
The following is the parameter block for the Availability report. You can copy it into a linked report based on the Availability report to replicate the controls of the base report.
"DownTime"
>Microsoft.SystemCenter.DataWarehouse.Report.Library!Microsoft.SystemCenter.DataWarehouse.Report.ParameterPrompt.AvailabilityDownTime</
Configuration reports in Operations Manager 2007 track changes in the properties of monitored objects. Following is a description of each Configuration generic report that includes a description of its report controls and report parameters. The parameter block of each report that can be copied into the definition of a linked report is also included.
Management Packs contain discoveries that collect object properties that are relevant for the management of the application. The data for the Configuration Changes report is derived from a delta-discovery done in the data warehouse where each discovery value is compared to the last known. If a change is detected, the changed property, the old and the new value and the time the change was discovered are recorded in the data warehouse.
The ID of the Configuration Changes report is Microsoft.SystemCenter.DataWarehouse.Report.ConfigurationChange.
The controls that are used in the Configuration Changes report are shown in the following table with the parameters that each populates.
The following is the parameter block for the Configuration Changes report. You can copy it into a linked report based on the Configuration report to replicate the controls of the base report.
A management pack contains discoveries that collect information specific to the management pack. For all selected objects the Custom Configuration report displays the properties discovered by management packs. By checking the box a property can be selected to be printed on the report. The controls to the right allow defining the order of the selected properties from left (higher in the parameter list) to right (lower in the parameter list).
The ID of the Custom Configuration report is Microsoft.SystemCenter.DataWarehouse.Report.CustomConfiguration.
The controls that are used in the Custom Configuration report are shown in the following table with the parameters that each populates.
Specifies the columns to be included in the output of the report and the columns that are used to filter the returned data. This is described below in more detail.
The Columns parameter defines the columns to include in the output of the report and the columns that are used to filter the output. The following table lists the values that are required to define each column.
ID Node
Specifies the node defining the ID of the property. If the Operations console is used, this will be the GUID of the property. This should be changed to an $MPElement variable so that the management pack can be transferred between management groups.
Specifies the attribute with a value of True or False that determines whether the column is displayed. If the value is False, the column is only used to filter the output.
Filter Node
If used, this node identifies the column as being used for filtering the output. The Type attribute can be either Contains or Equals, and the content of the node includes the text to match.
If the column should only be displayed, but not used for filtering, the filter node is not included.
All properties are included as a single parameter entry using the syntax shown in the following example. This example shows a report that uses the following parameters of the Microsoft.Windows.Computer class and is filtered for computers that include ‘srv’ in the name:
>$MPElement[Name="Windows!Microsoft.Windows.Computer"]/PrincipleName$</
>srv</
>$MPElement[Name="Windows!Microsoft.Windows.Computer"]/IPAddress$</
>$MPElement[Name="Windows!Microsoft.Windows.Computer"]/ActiveDirectorySite$</
The following is the parameter block for the Custom Configuration report. You can copy it into a linked report based on the Custom Configuration report to replicate the controls of the base report.
"Properties"