How to create a Service Level Objective in SCOM

The SLA tile displays gauges showing the availability of SCOM objects, such as servers or applications, based on your SCOM Monitor Service Level Objectives (SLOs).

Before the SLA tile can be used, you must have one or more Monitor SLOs defined in your SCOM management group.

SquaredUp DS does not support Collection Rule SLOs, or the unmonitored state which should not be ticked in the Monitor SLO configuration.

Creating an availability Service Level Objective for your distributed applications

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

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 AvailabilityDescription:<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.

    SquaredUp DS does not support Collection Rule service level objectives.

12. Enter the following details and click OKService level objective name:AvailabilityTargeted class:ServiceMonitor:AvailabilityService level objective goal:99.000Specify states:Critical is checked

    SquaredUp DS does not support unmonitored, and it should not be ticked.

13. Click Next. On the Summary page, click Finish

Was this article helpful?