> For the complete documentation index, see [llms.txt](https://help.highlight.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.highlight.net/reporting/network-reports/colours.md).
# Colours
### Colour Meaning for Issue Scores and Exceptions
Report showing Issue Scores and Exceptions
Above is a sample report output showing Issues and Exceptions. Colours used are explained in this table:
| Colour: | No colour, grey text | Blue | Yellow | Orange | Red |
| ---------------------- | -------------------- | -------------------------- | ----------------------------------------- | ------------------------------------------ | --------------- |
| 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 |
### Issue Score
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.
#### Link Health (bearers)
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
#### Performance Tests (all types)
The calculations to derive the three scores are:
**Availability**
% of tests which failed**Health**% of tests which completed outside target
**Load**
0 (there is no load equivalent for performance tests)
### Exception
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.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://help.highlight.net/reporting/network-reports/colours.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.