3 minute readApplies to: v4

Troubleshooting the SLA tile

Squared Up pulls service level data from the Operations Manager Data Warehouse. To verify that the the data shown in Squared Up matches that shown in SCOM, you can run a Service Level Tracking Summary Report.

Squared Up does not support Collection Rule SLOs or the unmonitored state.

If the percentage uptime shown in Squared Up does not match that shown in SCOM

Both Squared Up and SCOM Reporting pull data from the Data Warehouse, so any inconsistencies in figures are usually due to configuration differences.

  1. Check that both Squared Up and the Service Level Tracking Summary Report are using the same SLO.

    In Squared Up check the SLO selection section of the SLA tile configuration:

    SLA tile SLO section

    The SLO is specified in the Service Level Tracking Summary Report:

    SLO in the Service Level Tracking Summary Report

    Service Level Tracking Summary Report Config

  2. Check the configuration of the SLO. Specifically, that Unmonitored is not ticked. Squared Up does not support the unmonitored state.

  3. Check that your SCOM report is using the same timeframe as Squared Up.

    In Squared Up 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:

    Page Level Timeframe

    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:

    Tile Timeframe

    Check that the timeframe in the SCOM report matches that being used in Squared Up:

    Tile Timeframe

  4. Check that your SCOM report is using the same Data Aggregation as Squared Up for the timeframe.

    Data Aggregation setting in the SCOM report:

    Tile Timeframe

    Squared Up 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. 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) Squared Up will be probably be using daily data.

  5. If you are using an Availability report check that the downtime state options match those specified in the SLO. See How to check the configuration of an SLO. Run a Service Level Tracking Summary Report on the SLO.

  6. Change to an SLO that is working on another dashboard

  7. On the SCOM server restart the System Center Data Access Service.

How to use the SLA tile

How to create an Availability Report

How to create a Service Level Objective in SCOM

How to run a Service Level Tracking Summary Report

How to find the SCOM ID of an SLO

Collecting Diagnostic Information

How to check the configuration of an SLO

Squared Up Ltd. (c) 2018Report an issue with this article