This article only applies to Squared Up Version 2.0. If you're looking for help with Squared Up Version 3.0, please visit our new knowledge base

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


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.


To create a generic Service Level Objective for your distributed applications:


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, enter the following details and click Next:

  • Targeted class:

    • Click ‘Select…’

    • Use the ‘Search result filter’ dropdown to select ‘Distributed Application’

    • In the list, select ‘Service’ (from System Library)

    • Click OK

  • Scope: All objects of the targeted class

  • Management pack: Create a new management pack, for example ‘SlaTest’

7. On the ‘Service Level Objectives' page, enter the following details and click Next:

  • Click Add > Monitor state SLO (Note: Squared Up does not support Collection Rule SLOs).

  • Service level objective name = ‘Availability’

  • Targeted class = Service

  • Monitor = Availability

  • Service level objective goal = 99.000

  • Specify states = Critical checked (Note: Squared Up does not support 'unmonitored').

  • Click OK

8. On the ‘Summary’ page, click Finish


See also:

Troubleshooting SLA dashboards

How to check the configuration of an SLO