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
A Service Level Tracking Summary Report in SCOM can be useful if you wish to verify that the the data shown in Squared Up matches that shown in SCOM for a particular SLO.
1. First check the details of the SLA plugin in Squared Up.
Next we will configure the 'Service Level Tracking Summary Report' in SCOM:
2. In SCOM go to Reporting, then the Microsoft Service Level Report Library and double click on 'Service Level Tracking Summary Report'.
3. First we will choose either daily or hourly Data Aggregation. Squared Up uses hourly data by default as long as it is available for the whole reporting Timeframe, otherwise it uses daily data. If your Squared Up SLA plugin is configured with a Timeframe of 12 hours or 24 hours it will be using hourly data aggregation. For Timeframes over 2 days (i.e. 7 days, 30 days, 3 months, 6 months, 12 months) Squared Up will be using daily data aggregation.
If Timeframe > 2 days Squared Up uses Daily aggregated data.
|Squared Up Timeframe||Data Aggregation|
In my example my Squared Up SLA plugin is using a Timeframe of 30 days so this is using daily data, so I will change my SCOM 'Service Level Tracking Summary Report' from hourly to daily data aggregation.
4. Next we need to set the time period. For my 30 day Timeframe I can select Advanced in the From dropdown, and then change it from 'no offset' to 'minus' 30 days.
5. Click 'Add' and search for your SLO, in my case 'Windows Computer'. Select it, click 'Add' and then 'OK'.
6. Click 'Run' from the top left.
7. Check the results match those shown in Squared Up:
If the figures do not match you should check the configuration of the Service Level Objective (SLO), check again you are using the correct Data Aggregation setting, and run an Availability Report to examine downtime: