An Availability Report in SCOM can be useful if you wish to examine the downtime for a particular object when checking the data shown in SquaredUp DS matches that shown in SCOM. For comparing data between SquaredUp DS and SCOM it's best to run a Service level tracking summary report (see How to run a Service Level Tracking Summary Report in SCOM). If you've already run a Service Level Tracking Summary report and want more information on an object's downtime, this is how to run an Availability report.
SquaredUp DS does not support Collection Rule SLOs, or the unmonitored state which should not be ticked in the Monitor SLO configuration.
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 Availability 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.
In SCOM go to the Monitoring workspace.
Browse to or search for the Distributed Application, group or computer you are interested in.
Click Availability under Report Task on the right hand pane.
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 will be probably be using daily data.
Next we need to set the time period. For example, for a 30 day timeframe select Advanced in the From dropdown, and then change it from no offset to minus 30 days.
