> 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/overview/average-strength-indicators-in-monitoring-section.md). # Average strength indicators in Monitoring section In both the monitoring overview and match up view, under every market average odds value there is a dynamic colored bar (highlighted below), representing the ‘strength’ of that average value. This represents for every market, what % of the market (market being determined by the bookmaker list configured, considering the weighting, see chapter 3.5 of this manual for more on bookmaker list) has published their odds. When the average is ‘weaker’ i.e. not many bookmakers from the list have published, or only low weighted bookmakers have published the bar will appear orange and partially complete. As more bookmakers, and more weighted bookmakers publish their odds the bar will become green and be fuller. --- # 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/overview/average-strength-indicators-in-monitoring-section.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.