> For the complete documentation index, see [llms.txt](https://docs.cybus.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cybus.io/1-7-2/documentation/system-status/metrics.md).
# Metrics
1. On the navigation panel, click `System`.
2. Click `Metrics`.
3. The `Metrics` tabs shows a number of values collected throughout operational times.
## Overview
The metrics view provides two tables that present data.
### **Hourly Collected Metrics**
This table consists of the following columns:
* Date/Time - Date and Time of the snapshot
* Number of Datapoints - Number of connected Endpoints at the time instant of the snapshot
* Messages per hour - Number of messages transferred by the broker during the hour between the previous snapshot to the current one
### **Daily Collected Metrics**
This table consists of the following columns:
* Date - Date of commulated metrics
* Number of Datapoints - Number of connected Endpoints at the time instant of the daily snapshot
* Messages per day - Number of messages transferred by the broker during the day
The collected metrics are computed in two ways.
1. The Number of Datapoints are a snapshot at the end of the day
2. The Messages per day is the sum of all messages per hour for this specific date
---
# 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.cybus.io/1-7-2/documentation/system-status/metrics.md?ask=&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.
