How to create a Service Level Objective in SCOM

Before the SLA plugin can be used, you must have one or more Service Level Objectives defined in your SCOM management group.

Creating an availability Service Level Objective for your distributed applications

The following steps describe how to create a Service Level Objective that can be used for all of your Distributed Applications. If you already have Service Level Objectives configured in SCOM, you can use those.

Squared Up does not support Collection Rule service level objectives
  1. Open the SCOM Operations Console.

  2. Go to Authoring workspace (Authoring tab on bottom left).

  3. Select Authoring > Management Pack Objects > Service Level Tracking in the left-hand tree view.

  4. Click Create in the right-hand task pane.

  5. On the General page, enter the following details and click Next:

    Name: Service Availability

    Description: <leave blank>

  6. On the Objects to Track page click Select… next to Targeted class

  7. Set the Search result filter dropdown to Distributed Application

  8. In the list, select Service (from System Library). Click OK

  9. Ensure the Scope is set to All objects of the targeted class

  10. Click the New button to create a new management pack, for example SlaTest

  11. On the Service Level Objectives page Click Add > Monitor state SLO

  12. Enter the following details and click OK

    Service level objective name: Availability

    Targeted class: Service

    Monitor: Availability

    Service level objective goal: 99.000

    Specify states: Critical is checked

    Squared Up does not support ‘unmonitored’
  13. Click Next. On the Summary page, click Finish

label: How to create a Service Level Objective in SCOM keywords: SLO Service Level Objective SLA goal tracking monitor state