> For the complete documentation index, see [llms.txt](https://prosbcdocs.telcobridges.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://prosbcdocs.telcobridges.com/telecom-references/cdr-and-statistics/system-statistics.md).

# System Statistics

**This tool has been deprecated in version 2.8+**

System Statistics is a tool that allows the monitoring of the evolution of the system status. It gathers statistics at a fixed interval and stores them. Those statistics can then be used to generate graphs.

### Statistics Collection

The gathered statistics are determined by the Global Polling Level. By default, this value is set to Level 3. This means that only statistics level 3 or higher are queried. A list of all the available statistics for your system can be found on the [statistics dictionary](/telecom-references/cdr-and-statistics/statistics-dictionary.md) page.

Statistics are queried at a fixed interval. By default, this is set so statistics are queried once every 10 minutes. Once queried, the statistics are saved on disk for future use. If the statistics grow over a configurable size, statistics will be deleted starting by the oldest ones. This will, at most, delete a single day's statistics at a time.

### Loggable Statistics

* [ToolpackToolpack v2.7:Loggable Statistics](https://prosbcdocs.telcobridges.com/tmedia-documentation/other-pages/monitoring-and-statistics/loggable-statistics)


---

# 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://prosbcdocs.telcobridges.com/telecom-references/cdr-and-statistics/system-statistics.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.