Colours
Last updated
Was this helpful?
Last updated
Was this helpful?
Above is a sample report output showing Issues and Exceptions. Colours used are explained in this table:
Issue Scores (0 to 10)
0.0
0.1 - 0.5
0.6 - 1.0
1.1 - 2.5
2.6 - 10.0
Exceptions (hh:mm)
00.00 (0)
00:00 - 00:06
00:06+ - 01:00
01:00+ - 06:00
06:00+
Exceptions (in words)
00.00 (0)
up to and including 6 mins
more than 6 mins up to and including 1 hr
more than 1 hour up to and including 6 hrs
more than 6 hrs
An Issue Score is a number from 0 (good, no issues) to 10.0 (bad, lots of issues) which provides a simple way to see how good or bad a watch was during the selected time period and to compare it with other watches. Issue Scores are an aggregation of several metrics. Values are adjusted logarithmically so that small-medium problems push the score up quickly, and it then levels off.
The calculations to derive the three scores are:
Availability
the percentage of time the link was down, then adjusted down to a score out of 10
Health
error+discard packets per million transmitted/received, scaled so 10000 (or more) per million is 100%, then adjusted down to a score out of 10
Load
the percentage of time traffic exceeded 60% load, then adjusted down to a score out of 10
The calculations to derive the three scores are:
Availability
% of tests which failedHealth% of tests which completed outside target
Load
0 (there is no load equivalent for performance tests)
When any metric Highlight is monitoring (for example Load or Response Time) exceeds its target threshold for a certain length of time, it generates an Exception and causes the watch to change colour (green to amber and then red). The watch now stays in this ‘Exception’ state until the metric returns to normal. The Exceptions report counts the total number of times this watch went into an Exception state and the total time it spent in that state in hours and minutes.
