本文件已封存並已停止維護。

Create a Performance Rollup

更新日期: 2009年6月

適用於: Operations Manager 2007 R2

In this topic, the Performance rollup is introduced. Sample code is provided so that you can add this functionality to your management pack.

Performance Rollup

The performance rollup, also called a dependency monitor, is defined similarly to the health rollup. For more information on dependency monitor elements, see Management Packs, Rules, Monitors, and Tasks and Their Relation to Models (http://go.microsoft.com/fwlink/?linkid=152365).

Dependency Monitor

A dependency monitor for performance uses the same algorithm that is used in the dependency monitor for health. See the Create a Health Rollup topic for details on the types of algorithms that are available.


      <DependencyMonitor ID="Microsoft.SCX.Authoring.Guide.Computer.SampleAppPerformanceRollup" Accessibility="Public" Enabled="true" Target="Unix!Microsoft.Unix.Computer" ParentMonitorID="SystemHealth!System.Health.PerformanceState" Remotable="true" Priority="Normal" RelationshipType="Microsoft.Unix.ComputerHostsSampleApplication" MemberMonitor="SystemHealth!System.Health.PerformanceState">
        <Category>PerformanceHealth</Category>
        <Algorithm>WorstOf</Algorithm>
      </DependencyMonitor>

The <DependencyMonitor> falls under the <UnitMonitors> subsection in the <Monitors> section of the management pack.

Observe Performance Dependency Monitor

Before you add the dependency monitor, observe the performance dependency monitor.

To observe the performance dependency monitor:

  1. Open the Operations console.

  2. Open the Health Explorer view for the monitored server. A tree diagram of availability, configuration, and performance is displayed.

  3. Expand the performance node. Notice that hardware, operating system, and the UNIX heartbeat monitors are currently installed and monitoring the server.

  4. Add the performance dependency monitor code to the monitors section in the management pack, increment the version number located in the manifest <identity>, save the file, and then import the management pack into Operations Manager.

  5. Refresh the Health Explorer.

  6. Expand the performance node. The Microsoft.SCX.Authoring.Guide.Computer.SampleAppPerformanceRollup should now be included.

  7. Continue to expand the performance node tree until the Sample App Perf Monitor is visible.

Customization of Performance Dependency Monitor

Any monitor with a shared Parent Monitor ID can be combined into a single dependency grouping. The Dependency monitor ID is the description that is used in the Health Explorer. The Target is the same type that is used in the discovery: Unix!Microsoft.Unix.Computer. The Relationship Type is also UNIX-specific and defined as Microsoft.Unix.ComputerHostsSampleApplication. Changing the Parent Monitor ID and the dependency monitor ID creates a new dependency monitor in the Health Explorer.

顯示: