LogoDark mode logo
LogoDark mode logo
Contact SupportLoading Light/Dark Toggle

    • How to configure Operations Manager console integration with SquaredUp DS
    • How to run a Service Level Tracking Summary Report in SCOM
    • Putting a SCOM object into maintenance mode
    • How to make a user a SQL sysadmin
    • How to find the SCOM ID of an object or group
    • How to find the SCOM ID of an SLO
    • How to create an Availability Report in SCOM
    • How to create a Service Level Objective in SCOM
    • How to check the configuration of a Service Level Objective in SCOM
    • How to change where company knowledge is saved
    • How to enable HTML email notifications in SCOM
    • How to optimize the Data Warehouse - 5 Point Plan
  • Auditing
  • How to edit the Navigation Bar
  • How to check and modify the application pool identity
  • How to configure the session time-out
  • How to add links to an external ticketing system from Alerts
  • Using object properties in the SquaredUp DS URL
  • How to set up per-server configuration when using high availability (HA)
  • How to reconfigure SquaredUp DS after moving the Data Warehouse or SCOM server
  • How to check and reconfigure the Data Warehouse connection
  • How to reactivate your license
  • How to remove SquaredUp DS for SCOM

customizingscom sqlhow to run a service level tracking summary report in scom

How to run a Service Level Tracking Summary Report in SCOM

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

A Service Level Tracking Summary Report in SCOM can be useful if you wish to verify that the data shown in SquaredUp DS matches that shown in SCOM for a particular Service Level Object (SLO).

  1. First check the details of the SLA tile in SquaredUp DS. Click on the edit button 
    to edit the dashboard, and then the edit tile button 
    to open the tile configuration, and make a note of the following:
    Next, we will configure the Service Level Tracking Summary Report in SCOM:
    • Scope
    • Service Level Objective (SLO) name
    • Timeframe - If you have selected use page timeframe then the default page timeframe is 12 hours, which can be changed by the user at the top of the page.
  2. In SCOM go to the Reporting workspace, 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. SquaredUp DS 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 DS will be probably be using daily data.
  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 the Add button and search for your Service Level Object (SLO). Select it, click Add and then OK.
  6. Click the Run button at the top left.
  7. Check the results match those shown in SquaredUp DS:

If the figures do not match you should check the configuration of the SLO (see How to check the configuration of a Service Level Objective in SCOM) to ensure that unmonitored is not ticked, check again you are using the correct Data Aggregation setting, and run an Availability Report to examine downtime: How to create an Availability Report in SCOM.

Was this article helpful?


Have more questions or facing an issue?
Submit a ticket

Footer

Sites

  • SQUAREDUP
  • SQUAREDUP DS
  • DOWNLOAD
  • COMMUNITY ANSWERS

Quick Links

  • SUBMIT A REQUEST
  • EVENTS
  • CAREERS

Small Print

  • PRIVACY POLICY
  • TERMS AND CONDITIONS
Youtubex (Twitter)LinkedIn

© SquaredUp 2025