Uptime Calculation in Reports

Uptime is an important monitoring metric available in your monitors and reports: it shows uptime of your monitor as measured by monitoring check success or failure.

In most of your in-dashboard reports, you can choose to show in the report data of your monitors per individual location, or for all locations.

Click the link in the topmost right corner of your report screen to select the scope of your report.

Performance Report

You can then select one of the below options:

  • All Locations (to show data of your monitors across all locations)
  • All with Locations (to show data of your monitors grouped by location, as well as data across locations)
  • Any individual location in the list (to show data for your selected location)

Uptime in reports is calculated differently for an individual location and across all locations.

Uptime calculation methods used in reports are detailed further in this document.

 

Uptime Calculation for Individual Location

Note: the examples for different uptime calculation methods described herein and further in this document use one-hour data reporting (aggregation) interval.

If you select any location from the list, your report will show uptime of your monitors for the selected location.

Report for Individual Location

For all types of external monitoring (Uptime, Transaction and Full Page Load), an individual location’s uptime over a reporting (aggregation) interval is calculated by the following method:

  • The percentage of the location’s monitoring checks that have returned OK result out of all monitoring checks completed within the reporting (aggregation) interval:

    [Uptime individual location] = [Number of location’s checks that have returned OK result] / [All checks of the location within the reporting interval]*100%

The number of checks accomplished within the reporting (aggregation) interval depends on the monitoring check frequency that you have set for a particular location in your monitor’s settings.

Settings_

The number of checks within the reporting interval is equal to:

[Number of checks within reporting interval] = [Reporting interval]) / [Check frequency interval]

So if e.g. you have configured check frequency for your monitor from US-MID location to be 3 min, the total number of checks within the one-hour interval will be equal to:

60/3 = 20

Example: uptime calculation for an individual location for Uptime monitors

The below example illustrates the described individual location uptime calculation method for an Uptime monitor.

The example uses one-hour reporting interval.

Report-screenshot-2

In the example, the user has configured monitoring from 4 locations, with the check frequencies as follows:

  • LOC 1: 1 min
  • LOC 2: 2 min
  • LOC 3: 3 min
  • LOC 4: 5 min

Calculating by the above described method, for the one-hour reporting (aggregation) interval:

  • Location 1: [Number of checks that have returned OK result] / [All checks] * 100%= 26 / 60 * 100% = 43%
  • Location 2: [Number of checks that have returned OK result] / [All checks] * 100% = 10 / 30 * 100%= 33%
  • Location 3: [Number of checks that have returned OK result] / [All checks] * 100% = 6 / 20 * 100% = 30%
  • Location 4: [Number of checks that have returned OK result] / [All checks] * 100% = 4 / 12 * 100%= 33%

Example: uptime calculation for individual location for Transaction/FPL monitors

The below example illustrates the described individual location uptime calculation method for a Transaction (or, similarly, a Full Page Load) monitor.

The uptime calculation method is the same as for uptime monitors.

The example uses one-hour reporting interval.

Report-screenshot-3

 

In the example, the user has configured monitoring from 4 locations, with the check frequencies as follows:

  • LOC 1: 5 min (currently the minimum check frequency currently available for Transaction and Full Page Load monitors)
  • LOC 2: 10 min
  • LOC 3: 15 min
  • LOC 4: 20 min

Calculating by the above described method for all external monitors, for the one-hour reporting (aggregation) interval:

      • Location 1: [Number of checks that have returned OK result] / [All checks] * 100%= 6 / 12 * 100% = 50%
      • Location 2: [Number of checks that have returned OK result] / [All checks] * 100% = 2 / 6 * 100%= 33%
      • Location 3: [Number of checks that have returned OK result] / [All checks] * 100% = 3 / 4 * 100% = 75%

  • Location 4: [Number of checks that have returned OK result] / [All checks] * 100% = 1 / 3 * 100%= 33%

All with Locations

If you select “All with Locations” from the list, your report will show uptime of your monitors grouped by location for your specified time range.
All_With_Locations_

“All with Locations” uptime uses the same calculation method for individual locations as described above: it just consolidates your monitors by location in the report.

Notice that “All with Locations” option shows also the “All Locations” data, which is available also in a separate “All Locations” option in the report scope selection combo box, as described further in this document.

Uptime Calculation for All Locations

If you select “All Locations” from the list, your report will show uptime of your monitors across all locations for the set time range.

For all types of external monitors (Uptime, Transaction and Full Page Load) the “All Locations” uptime is calculated by the following method:

– As different locations for a monitor may have different check frequency intervals set by the user (see Uptime Monitoring, Transaction Monitoring and Full Page Load Monitoring), the smallest check frequency interval among all locations is taken to determine uptime across all locations for each such interval. If, for example, the user has set monitoring check frequencies from different locations to be 1, 2, 3 and 5 min, then 1 min is the smallest check frequency interval among all locations.

– For each of the smallest check frequency intervals, locations that do not run check during that interval are excluded when determining the “All Locations” uptime.

– For each of the smallest check frequency intervals, if there is at least one OK result returned by a location, then the “All Locations” uptime check result for that interval is assigned OK status. If all locations running checks within that smallest check frequency interval return NOK, the “All Locations” uptime check result for that interval is assigned NOK status.

– For every reporting interval (one hour in our example), the “All Locations” uptime result is then determined as follows:

– The percentage of the smallest frequency interval checks that have returned OK result (as per the above rule) out of the number of smallest check frequency intervals in the reporting interval.

[Uptime “All Locations”] = [Number of smallest frequency interval checks that returned OK Result] / [Number of all smallest check frequency intervals] * 100%

The number of checks within the reporting interval is equal to:

[Number of Checks] = [Reporting interval] / [Smallest check frequency interval]

That means that if, for example, the smallest check frequency interval for a monitor among all locations is 1 min then the number of smallest check frequency intervals in the reporting interval of one hour would be:

60/1 = 60

If the smallest check interval is 2 min, the number of smallest check frequency intervals in the reporting interval of 1 hour would be:

60/2 = 30

Example: calculation of “All Locations” uptime for Uptime monitors

The below example illustrates the described “All Locations” uptime calculation method for uptime monitors. The example uses one-hour reporting interval.
Report-screenshot-4

In the example, the user has configured monitoring for an Uptime monitor from 4 locations, with the check frequencies set for locations as follows:

  • LOC 1: 1 min
  • LOC 2: 2 min
  • LOC 3: 3 min
  • LOC 4: 5 min

The smallest check frequency interval among all locations is 1 min, so “All Locations” uptime status (OK or NOK) is determined every 1 min during the one-hour reporting interval, as shown in the example.

The number of one-minute check intervals within the reporting interval (one hour in our example) will be:

60/1 = 60

As shown in the example, e.g. the 2nd minute check has returned:

  • LOC 1: OK
  • LOC 2: NOK
  • LOC 3: no check carried out, as 3 min check frequency interval is set for this location
  • LOC 4: no check carried out, as 5 min check frequency interval is set for this location

As there is at least one OK result returned by a location, “All Locations” uptime status is assigned OK for this smallest check frequency interval, as shown in the example.

Now, it we look e.g. at the results of the 5th min check, we can see that:

  • LOC 1: NOK
  • LOC 2: no check carried out, as 2 min check frequency interval is set for this location
  • LOC 3: no check carried out, as 3 min check frequency interval is set for this location
  • LOC 4: NOK

As there is not at least one OK result returned by a location within this check interval, “All Locations” uptime status is assigned NOK for this smallest check frequency interval, as shown in the example.

If we count now the number of “All Locations” OK results out of all the smallest check frequency intervals in the reporting interval (one-hour), in the shown example there are:

  • Total number of the smallest check frequency intervals: 60
  • OK results: 33
  • NOK results: 27

Calculating by the above formula, the “All Locations” uptime for the shown reporting interval of one-hour will be:

33 / 60 * 100% = 55%

Note: if due to a technical reason a location delays reporting the check data, the location will be excluded from calculations in that smallest check frequency interval.

 

Example: calculation of “All Locations” uptime for Transaction/FPL monitors

The below example illustrates the described individual location uptime calculation method for a Transaction (or, similarly, a Full Page Load) monitor.

The uptime calculation method is the same as for uptime monitors.

The example uses one-hour reporting interval.

Report-screenshot-5

In the example, the user has configured monitoring for a Transaction monitor from 4 locations, with the check frequencies set for locations as follows:

  • LOC 1: 5 min (currently the minimum available frequency for Transaction and Full Page Load monitors)
  • LOC 2: 10 min
  • LOC 3: 15 min
  • LOC 4: 20 min

The smallest check frequency interval among all locations is 5 min, so “All Locations” uptime status (OK or NOK) is determined every 5 min during the one-hour reporting interval, as shown in the example.

The number of five-minute check intervals within the reporting interval (one hour in our example) will be:

60/5 = 12

As shown in the example, e.g. the 5th minute check has returned:

  • LOC 1: NOK
  • LOC 2: no check carried out, as 10 min check frequency interval is set for this location
  • LOC 3: no check carried out, as 15 min check frequency interval is set for this location
  • LOC 4: no check carried out, as 20 min check frequency interval is set for this location

As there is not at least one OK result returned by a location within this check interval, “All Locations” uptime status is assigned NOK for this smallest check frequency interval, as shown in the example.

Now, it we look e.g. at the results of the 10th min check, we can see that:

  • LOC 1: OK
  • LOC 2: NOK
  • LOC 3: no check carried out, as 15 min check frequency interval is set for this location
  • LOC 4: no check carried out, as 20 min check frequency interval is set for this location

As there is at least one OK result returned by a location, “All Locations” uptime status is assigned OK for this smallest check frequency interval, as shown in the example.

If we count now the number of “All Locations” OK results out of all the smallest check frequency intervals in the reporting interval (one-hour), in the shown example there are:

  • Total number of the smallest check frequency intervals: 12
  • OK results: 8
  • NOK results: 4

Calculating by the above formula, the “All Locations” uptime for the shown reporting interval of one-hour will be:

8 / 12 * 100% = 67%

Note: if due to a technical reason a location delays reporting the check data, the location will be excluded from calculations in that smallest check frequency interval.

 

“All Locations” Uptime Calculation for Different Reporting Intervals

Different reports may be using different reporting (aggregation) intervals.

For any reporting interval the “All Locations” uptime calculation is done by the same method as described above. The count of monitoring checks and OK results is taken for the reporting interval used in the report (e.g. daily), in the same way as in the above described example of hourly reporting interval.