> 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/hotlisting-and-alert-score-comments-match-id.md). # Hotlisting and alert score, comments, match ID Any event in the monitoring overview can be quickly added to the hotlist by clicking the star beside it. When the star turns yellow, the event is added to the hotlist. Once an event is added to the hotlist, it can be quickly accessed in the monitoring overview and in the Alerts section using the 'Hotlisted' quick filter. {% @storylane/embed subdomain="app" linkValue="q92wpncwaumk" url="" %} The alert score is displayed beside each event and represents a combination of all active alerts for that event. A higher alert score indicates greater potential exposure. Therefore, events with a high alert score should be addressed immediately. Red alert scores are classified as emergencies and require immediate attention, while orange alerts are non-emergencies but should still be addressed as soon as practicable. Further details on these alerts can be found in Section 8 of this manual. Clicking on the alert score will open a pop-up displaying details of the alerts and the specific factors that contributed to the score. It also provides an overview of critical markets (own odds vs market average). The speech bubble pictogram next to the alert score opens a pop-up displaying comments and logs related to the event. The two numbers beside the pictogram indicate the count of user-added comments and automatic log entries, respectively. From here, the user can leave a comment visible to all other users within the same account or view a log of all alert-related actions taken by users for that event. Within the comments pop-up, users can mute alerts related to the event completely, until a specified alert score is reached, for a selected period of time, or until a pre-defined time before the event starts. Additionally, users can unmute the alerts at any time. Muting an alert differs from disabling an alert (see Chapter 4.2.6 of this manual). Any muting action taken by a user will be recorded in the log for future reference. Events with comments can be quickly viewed in the monitoring overview and in the Alerts section using the ‘Commented’ quick filter (see Sections 4.1.1 and 8 of this manual). In the monitoring overview screen, users can quickly suspend an event by clicking ‘Suspend.’ To unsuspend it, they can click the same button, now labeled ‘Publish. Own odds for suspended matches will be displayed in grey, instead of blue or pink (see the screenshot below for an example of a suspended and an active event).
{% hint style="info" %} You cannot suspend a market that is set to ‘Mon’ via ‘Overview’ in the config. These markets are already effectively suspended because they are not being offered by the user and are only visible for monitoring purposes. \+ MATCH ID {% endhint %} --- # 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/hotlisting-and-alert-score-comments-match-id.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.