Defining Reports
適用於: System Center Operations Manager 2007
You can plan a set of reports in an Operations Manager 2007 management pack by determining a basic reporting strategy. That is, if you at all include any reports in the management pack. If you plan to include linked reports in your management pack, then you should define a set of reports that most effectively provide a valuable set of data to the user.
Determine Report Strategy
There are three options for including reports in a management pack.
No Reports
All the data that is collected by a management pack can be accessed from the generic reports that are automatically installed with Operations Manager Reporting. The only requirement for the author is to make sure that the management pack includes rules that collect the required data to the data warehouse. Therefore, users of your management pack will have access to reports whether you give them your management pack.
Linked Reports
Although users can access generic reports for data collected by any management pack, each user is responsible both for determining what information is important and for selecting values for different report parameters. Providing custom reports or linked reports in the management pack lets you direct the user to important information. In addition, this lets the user run different reports that have a minimal number of options.
Linked reports provide a strategy for you to include generic reports in your management pack customized for your application. This enables the user to provide a minimum of configuration to run the report and means that important parameters have correct values. Linked reports require much less work than creating than a custom report and frequently will be sufficient for the reporting requirements of the application that you are monitoring.
Custom Reports
Custom reports allow for full customization of the report both in the data that is retrieved and in how the report is formatted. Custom reports are written in Report Definition Language (RDL) and can provide any option enabled by Microsoft SQL Server Reporting Services. The complete RDL for the report is included in the management pack.
Creating a custom reports require significantly more effort than creating a linked report and requires detailed knowledge both in writing a query to retrieve data from a SQL Server database and in creating a report for SQL Reporting Services. Because of the additional skills and effort required, the only time that you should create a custom report instead of a linked report is if your reporting requirement cannot be met by one of the generic reports.
Custom reports are beyond the scope of this guide. 如需 custom reports, see Overview of Reporting in Operations Manager 2007.
Recommended Reports
The following are recommendations for when each kind of linked report should be included in a management pack. Other kinds of reports might be included, depending on the requirements of your particular application and the preference of users. However, these are the most common reports for a many management packs for different applications.
Availability Reports
You should include an availability report for top level application or application role classes. These are classes that use such base classes as Distributed Application, Windows Computer Role, or Windows Local Application and frequently provide a health rollup for other classes. Such a report provides a history of the availability for an application or a significant component of an application.
Availability reports for component of the application, such as classes based on Windows Application Component, are less important because their availability is included in the availability of their hosting class. You can access the availability of these objects by drilling into the availability of the higher level objects when the report is run. State views should still typically be provided for classes to give the user a quick view of their current state. Historical analysis of availability over periods of time, which is the focus of availability reports, is typically more valuable with higher level objects.
Configuration Reports
You should include configuration reports for classes in your management pack that include custom properties, especially if changes in these properties indicate significant configuration of the application being monitored. Configuration reports show any changes to these properties that occurred in the time duration of the report. Regular review of configuration reports can warn you about unexpected configuration changes. They can also be valuable in identifying when particular changes were made because they may coincide with changes to the availability or performance of the application.
For example, the SQL Server 2008 (Monitoring) management pack includes a report named SQL Server Configuration that includes all properties for the SQL DB Engine class. A separate configuration report named SQL Server Servicepack Report includes only the Version and Service Pack Version properties of the class to quickly identify the service pack history of any SQL Server installations. Both reports have filters to ensure that the user can only select the SQL DB Engine class when they run them.
Performance Reports
You should include performance reports in any management pack that collects performance data. Although you can always use one of the generic performance reports to access interesting performance counters, these require lots of customization, especially if the report contains multiple series.
Linked performance reports let you create individual reports that combine related performance counters for a particular class of object. An effective strategy is to create a separate linked report for each class and potentially for different sets of related counters for each class.
An example of this strategy is provided in the Windows Server 2008 Operating System (Monitoring) management pack. Separate performance linked reports are included for classes such as Windows Server 2008 Logical Disk and Windows Operating System. Multiple linked reports are included for each class combing related sets of counters that can be analyzed together in a single report. Each linked report includes a filter on the Object XML Picker control that ensures that only the correct class can be selected.