> For the complete documentation index, see [llms.txt](https://docs.nexthink.com/platform/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nexthink.com/platform/references/references-classic/search-and-information-display-classic/engine-data-history-classic.md).
# Engine data history (classic)
Nexthink Portal provides an administration page so you can check the current state of data history on each connected Engine. You can access this feature by clicking on the gear icon in the main navigation bar and then selecting the **Engines** administration dashboard.
All the Engine instances associated with Portal are listed in a table view and the system automatically retrieves the following information from the connected ones:
* **First event**
The date and time of the very first event stored in the Engine database.
* **Last event**
The date and time of the last event recorded in the Engine database.
* **Available data**
The elapsed time between the first and the last event, reported in days.
---
# 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.nexthink.com/platform/references/references-classic/search-and-information-display-classic/engine-data-history-classic.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.
