> For the complete documentation index, see [llms.txt](https://docs.eseye.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eseye.com/hera604/diagnostics-and-maintenance/data-logging-and-performance.md).
# Data Logging & Performance
Diagnose common Hera 600 connectivity and management issues.
Open **Diagnostics & Maintenance > Data Logging > Settings** to control periodic collection of performance data.
| Field | Value shown | Description |
| ---------- | ------------- | ---------------------------------------------------------------------------------------------- |
| Logging | `Enabled` | Enables or disables data logging. |
| Log period | `900` seconds | Time between data-capture events. Shorter periods provide more detail but create more records. |
#### Performance
Open **Diagnostics & Maintenance > Data Logging > Performance** to view logged mobile signal and traffic data over time.
Use the date and time controls to select the period displayed. The graphs show:
* Mobile signal strength over time, measured in dBm.
* Mobile data sent and received over time.
* The mobile network operator associated with the selected period.
Hover over a graph point to view its exact value and timestamp. Hover over the network-operator bar to view the operator name. Use the data to identify recurring loss of signal, changes of mobile network, or unusual traffic patterns; compare any event with router logs and site activity before drawing a conclusion.
---
# 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.eseye.com/hera604/diagnostics-and-maintenance/data-logging-and-performance.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.
