How to use the SLA tile
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).
How to configure an SLA tile
Before the SLA tile can be used, you must have one or more Monitor SLOs created in your SCOM management group.How to create a Monitor Service Level Objective (SLO) in your SCOM console
- Open the SCOM Operations Console.
- Go to Authoring workspace (Authoring tab on bottom left).
- Select Authoring > Management Pack Objects > Service Level Tracking in the left-hand tree view.
- Click Create in the right-hand task pane.
On the General page, enter the following details and click Next:
- On the Objects to Track page click Select... next to Targeted class
- Set the Search result filter dropdown to Distributed Application
- In the list, select Service (from System Library). Click OK
- Ensure the Scope is set to All objects of the targeted class
- Click the New button to create a new management pack, for example
On the Service Level Objectives page click Add > Monitor state SLO.
SquaredUp does not support Collection Rule service level objectives.
Enter the following details and click OK
Service level objective name:Availability
Service level objective goal:99.000
Specify states:Critical is checked
SquaredUp does not support unmonitored, and it should not be ticked.
- Click Next. On the Summary page, click Finish
Add a new tile to a dashboard or perspective and choose the SLA tile.
See How to scope tiles on dashboardsand How to scope tiles on perspectives. For information on advanced options, such as how to only show objects that are not healthy take a look at How to use criteria when scoping objects.Scope examples
To view Distributed Applications (DAs) select advanced then in the class box type
user created distributed application.
To show the SLA of a group itself, use the list option and type in the name of your group.
To show the SLA of members of a group use the group option with your group name.
Click on the drop down list and select the Monitor SLO from SCOM that you wish to use.
The slo selection drop down only lists the Monitor SLOs from SCOM. SquaredUp does not support Collection Rule SLOs, or the unmonitored state,
This is the timeframe over which the SLA will be calculated. Hourly aggregated data will be used if it exists for the whole of the interval, if not then daily aggregated data is used.
You can either choose a specific timeframe or allow the tile to adapt to the page timeframe.What is the page timeframe?
The page timeframe is the timeframe setting a dashboard or perspective is currently using. When a user changes the page timeframe, all tiles that use the page timeframe will adapt to the new timeframe. Tiles that don't use the dynamic page timeframe aren't affected and won't change.
Here you can define how the SLA gauges are displayed.
tile (large SLA gauge, more details, useful for a large impact wallboard):
inline (smaller SLA gauge, list format to display more objects):
Allows you to remove the status icon, label or SLA gauge.
Allows you to change the label next to the status icon. You can also create a custom label (see How to use Custom Labels).
Click done to save the tile.
The tile now shows data according to your settings.
If when displaying the status and SLA of groups themselves (adding groups to scope > list for example) one or more groups have missing SLA gauges and the health status is shown as grey with a question mark, this means that the group does not have a Dependency Roll Up Monitor.
SquaredUp pulls service level data from the Operations Manager Data Warehouse. To verify that the data shown in SquaredUp matches that shown in SCOM, you can run a Service Level Tracking Summary Report (see How to run a Service Level Tracking Summary Report in SCOM).
SquaredUp does not support Collection Rule SLOs, or the unmonitored state.
Both SquaredUp and SCOM Reporting pull data from the Data Warehouse, so any inconsistencies in figures are usually due to configuration differences.
Check that both SquaredUp and the Service Level Tracking Summary Report are using the same SLO.
In SquaredUp check the SLO selection section of the SLA tile configuration:
The SLO is specified in the Service Level Tracking Summary Report:
Check the configuration of the SLO (see How to check the configuration of a Service Level Objective in SCOM). Specifically, that Unmonitored is not ticked.
SquaredUp does not support the unmonitored state, and it should not be ticked.
Check that your SCOM report is using the same timeframe as SquaredUp.
In SquaredUp if the tile timeframe is set to use page timeframe then the user can change the timeframe from the default of 12 hours using the buttons at the top of the page:
If the tile timeframe is set to specific timeframe then if a user clicks the page level times at the top of the page, the timeframe will not change:
Check that the timeframe in the SCOM report matches that being used in SquaredUp:
Check that your SCOM report is using the same Data Aggregation as SquaredUp for the timeframe.
Data Aggregation setting in the SCOM report:
SquaredUp uses hourly data by default as long as it is available for the whole reporting timeframe, otherwise it uses daily data. Whether hourly data is available for the whole timeframe will depend on your Data Warehouse data retention settings (see How to optimise the Data Warehouse - 5 Point Plan). For a timeframe of 12 or 24 hours it will probably be using hourly data aggregation, for timeframes over 2 days (i.e. 7 days, 30 days, 3 months, 6 months, 12 months) SquaredUp will be probably be using daily data.
- If you are using an Availability report (see How to create an Availability Report in SCOM) check that the downtime state options match those specified in the SLO. See How to check the configuration of a Service Level Objective in SCOM. Run a Service Level Tracking Summary Report on the SLO (see How to run a Service Level Tracking Summary Report in SCOM).
- Change to an SLO that is working on another dashboard
- On the SCOM server restart the System Center Data Access Service.