> For the complete documentation index, see [llms.txt](https://docs.sportradar.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sportradar.com/ctrl/guide/monitoring.md).
# Monitoring
The Monitoring screen serves as the home screen of the Ctrl interface, where the user will spend the majority of their time. Monitoring is broadly split into two main views: monitoring overview and monitoring Match Up view.
Throughout the monitoring section of Ctrl, odds across all markets will generally appear in blue, pink, or grey. Blue means that the odds have recently been shortening, or ‘cooling off’. Pink indicates that the odds have been increasing, or ‘heating up’. Odds shown in grey represent a market that is currently suspended. The depth of the coloration, in turn, indicates how recently a change has taken place; the coloration fades over time.
### Overview
The monitoring overview is a high-level view of all the sports, categories, and events that Ctrl offers. It presents a quick ‘headline’ look at the critical odds (for example, 3-way, total and handicap markets in soccer) for each event and how these compare to the market average. Market average odds are displayed after being ‘normalized’, to represent what they would be if all bookmakers were applying the same key as the user, to enable meaningful comparison.
For each event there is also an indication if the odds have been modified to semi-automatic or manual trading mode (see screenshot below), or if the margin on any of that event’s model driving markets has been skewed. A ‘BR’ box alongside shows that the event has officially been set up by Betradar, meaning that we can guarantee the event is genuinely taking place and that we have verified the correct start time of the event.
By clicking on the three dots, the user can access Head-to-Head Statistics, Settlements, and Archive pages for that event, as well as copy the match ID and regenerate alerts (**see screenshot below**).
---
# 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://docs.sportradar.com/ctrl/guide/monitoring.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.