> For the complete documentation index, see [llms.txt](https://docs.lsports.eu/u/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lsports.eu/u/coverage-hub/monitoring.md).

# Monitoring

Real-time fixture and odds monitoring

Monitor all active fixtures and provider coverage in real-time. Track which providers are offering which markets and see live odds updates.

<figure><img src="https://2846470291-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ftv77Uhe1UsyYNAhnfDk8%2Fuploads%2Fgit-blob-c6f5fbe76ab2b2cf5f990b980fbb321b999020b3%2Fcoverage-hub-monitoring.png?alt=media&amp;token=cee1893c-363f-4a9b-9bd9-0402d316c0b4" alt="Monitoring"><figcaption><p>Real-time fixture monitoring with live scores</p></figcaption></figure>

***

## Overview

The Monitoring system provides:

* Real-time fixture tracking across all sports
* Provider market and odds visibility
* Fixture status monitoring (InPlay and PreMatch)
* Quick access to detailed fixture data

***

## Fixture Status

### InPlay

| Status             | Description                                                  |
| ------------------ | ------------------------------------------------------------ |
| **NSY**            | Not Started Yet — fixture with open odds, start date in past |
| **About to Start** | Match beginning soon                                         |
| **In Progress**    | Match currently active                                       |
| **Interrupted**    | Displayed for 48 hours from start date                       |

**Not displayed:** Lost Coverage, Finished

### PreMatch

| Status             | Description                                    |
| ------------------ | ---------------------------------------------- |
| **NSY**            | Not Started Yet — displayed until match starts |
| **About to Start** | Displayed until InPlay status                  |

**Not displayed:** Postponed, Abandoned, Finished, Canceled

***

## Display Features

### Sports Bar

Sports are ordered by fixture count — the sport with the most fixtures appears first.

### Odds Format

Available formats:

* Decimal (default)
* Fractional
* American
* Malay
* Indonesian
* Hong Kong

### Racing Sports

For racing (PreMatch), columns include:

* Location
* Competition
* Races (with round number and start time)

***

## Views

| View                                                         | Description                 |
| ------------------------------------------------------------ | --------------------------- |
| [Provider View](/u/coverage-hub/monitoring/provider-view.md) | Analyze markets by provider |
| [Market View](/u/coverage-hub/monitoring/market-view.md)     | Analyze providers by market |

***

## Related

* [Coverage Hub Overview](/u/coverage-hub/coverage-hub.md) — Main Coverage Hub documentation
* [BOOST Overview](/u/boost/boost.md) — Main BOOST documentation


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.lsports.eu/u/coverage-hub/monitoring.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
