Calculation of Average Step Duration in Custom Transaction Reports

Custom Transaction Report (see Custom Reports) shows the average step duration in your transaction flow, by step or step group, for the selected period of time.Edit Transaction Reports

Roll mouse cursor over any of the bars in the chart to see the average duration of the step or step group for the selected time period.
Transaction Step Report

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

You can then select one of the below options:

  • All Locations (shows data of your monitors across all locations)
  • Any individual location in the list (to show data for your selected location)


Transaction step (or step group) duration in reports is calculated differently for an individual location and across all locations.

Transaction step calculation methods are detailed below.

 

Transaction Step Duration Calculation for Individual Location

Note: the examples for different transaction step duration 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 transaction step (or step group) duration of your monitors for the selected location.Transaction Step Report Location

Average step duration for individual location is calculated by the following method:

  • The average duration of the transaction step (or step group) of monitoring checks that have returned OK uptime result out of all monitoring checks of the location completed within the reporting (aggregation) interval:

    [Average transaction step (step group) duration individual location] = [Average transaction step (step group) duration of checks that returned OK result] = [Sum of transaction step (step group) durations of checks that returned OK result] / [Number of checks that returned OK result]

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 period is equal to:

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

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

60/5 = 12

Example: transaction step calculation for an individual location

The below example illustrates the described transaction step duration calculation method for an individual location.

The example uses one-hour reporting interval.

Report-screenshot-10

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

  • LOC 1: 5 min
  • LOC 2: 10 min
  • LOC 3: 15 min
  • LOC 4: 20 min

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

  • Location 1: [Sum of step (step group) durations of checks that have returned OK result] / [Number of checks that have returned OK result] = 65/9 = 7.2 sec
  • Location 2: [Sum of step (step group) durations of checks that have returned OK result] / [Number of checks that have returned OK result] = 36/4 = 9 sec

  • Location 3: [Sum of step (step group) durations of checks that have returned OK result] / [Number of checks that have returned OK result] = 21/3 = 7 sec
  • Location 4: [Sum of step (step group) durations of checks that have returned OK result] / [Number of checks that have returned OK result] = 8/2 = 4 sec

 

Transaction Step Duration Calculation for All Locations

If you select “All Locations” from the list, your report will show transaction step (or step group) duration of your monitors across all locations for the set time range.

Transaction Step Report With all Locations

“All Locations” transaction step (step group) duration is calculated by the following method:

– As different locations for a monitor may have different check frequency intervals set by the user (see Transaction Monitoring), the smallest check frequency interval among all locations is taken to determine the transaction step duration time across all locations for each such interval. If, for example, the user has set monitoring check frequencies from different locations to be 5, 10, 15 and 20 min, then 5 min is the smallest check frequency interval.

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

– 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 check within that interval return NOK, the “All Locations” uptime check result for that interval is assigned NOK status (see Uptime Calculation in Reports).

– For every reporting interval (1 hour in our example), the “All Locations” average transaction step duration result is then calculated as follows:

– The smallest frequency interval checks that have returned NOK as the “All Locations” uptime status are excluded from average transaction step calculation for the reporting interval.

– For each of the smallest check frequency intervals that have returned OK as the “All Locations” uptime status, the minimum transaction step duration reported by a location during that interval is determined as “All Locations” transaction step duration for that interval.

– The “All Locations” transaction step duration for the reporting interval is then calculated as an average of the minimum transaction step durations of the smallest check frequency intervals that have returned OK as an uptime status.

[Average transaction step duration “All Locations”] = [Average of minimum transaction step durations of the smallest frequency interval checks that have returned OK uptime status]
The number of checks within the reporting period 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 would be:

60/2 = 30

Example: calculation of “All Locations” average transaction step duration

The example below illustrates the described calculation method for average transaction step duration.

The example uses one-hour reporting interval.

Report-screenshot-1In the shown 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
  • LOC 2: 10 min
  • LOC 3: 15 min
  • LOC 4: 20 min

The smallest check frequency interval 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. for the 30th minute the check has returned:

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

Note that the checks from locations that have returned OK result show the transaction step duration values (msec).

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.

The transaction step duration per location for the 30th minute check in the example is:

– LOC 1: N/A, as the check result is NOK

– LOC 2: 9 msec

– LOC 3: 11 msec

– LOC 4: N/A, as no check run

As it can be seen, the minimum transaction step duration returned by a location (locations that have not run check or returned NOK omitted) is 9 msec returned by Location 1.

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

  • LOC 1: NOK
  • 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 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. Therefore, this 5-min interval will be omitted in calculation of “All Locations” average transaction step duration for the reporting interval (1 hour in the example).

 

Now, if we calculate the average of minimum transaction step durations of the smallest check intervals (5 min in our example) that have returned OK as “All Locations” uptime result within the reporting interval (1 hour in our example), for the shown example it will be:

[Average transaction step duration “All Locations”] = 64 / 10 = 6.4 msec

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

 

“All Locations” Transaction Step Calculation for Different Reporting Intervals

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

For any reporting interval the “All Locations” calculation of average transaction step (step group) duration is done by the same methods 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 one-hour reporting interval.