Defining a service level objective against an application

  • Article

Applies To: Operations Manager 2007 R2, Operations Manager 2007 SP1

You can configure a service level objective (SLO) to define the availability and performance goals for an application. In the following procedure, you create a new service level (LOB Application 1) against a distributed application, define a Monitor SLO that is based on availability (99.9% up-time), and define a Collection Rule SLO that is based on a performance rule (80% average processor time).

To define a service level objective for an application

  1. In the Operations console, from the Authoring view, click Management Pack Objects and then click Service Level Tracking in the Authoring navigation tree.

  2. In the Actions pane, click Create.

  3. Type a name for the service level that you are defining. For example, type LOB Application 1. Optionally, you can provide a description. Click Next.

  4. Under Targeted class, click Select to specify the class for the service level, such as Distributed Application. You can search for a class by typing it into the Look For field. Select the class for the service level and click OK.

  5. You can optionally change the scope for the service level by targeting all objects in a class or by targeting a specific group.

  6. Select the management pack where this service level will be saved. You can use an existing management pack or create a new one.

    Note

    By default, Operations Manager saves the setting to the Default Management Pack. As a best practice, you should create a separate management pack for service level tracking and save all service levels there.

  7. Click Next.

  8. On the Service Level Objectives page, click Add, and then click Monitor state SLO to create a new monitor. This monitor will track the availability of the application.

  9. Define the state monitor as follows:

    1. Type a name for the service level objective. For this scenario, type Availability.

    2. Under Monitor, choose the specific monitor that you want to use to measure the objective. For this scenario, choose Availability.

    3. For the service level objective goal, provide the numerical measure for your objective. For example, select 99.990 to indicate that your goal is 99.99% availability.

    4. You can refine what the monitor tracks as available by selecting or clearing any of the following state criteria:

      • Unplanned maintenance

      • Unmonitored

      • Monitoring unavailable

      • Monitor disabled

      • Planned maintenance

      • Warning

    5. Click OK.

  10. On the Service Level Objectives page, click Add, and then click Collection rule SLO to create a new collection rule. This rule will track the performance of the application

  11. Define the performance collection rule as follows:

    1. Type a name for the service level objective. For this scenario, type Performance.

    2. Specify the target class for the rule. Note that this class must be contained in the distributed application. For this scenario, select Windows Operating System.

    3. Specify the performance collection rule to use. For this scenario, choose Collect Processor\ % Processor Time performance counter.

    4. Choose one of the following aggregation methods:

      • Average

      • Min

      • Max

    5. Define the service level object goal by choosing either Less than or More than and entering a value. For this scenario, choose Less Than and 80. This indicates that the performance goal is to never exceed 80% processor time.

    6. Click OK.

  12. On the Service Level Objectives page, click Next.

  13. Review the summary, and click Finish.

  14. When the Completion page appears, click Close.

To validate the creation of the service level objective

  • In the Service Level Tracking pane, select the new service level, and click Properties in the Action pane.