> For the complete documentation index, see [llms.txt](https://navixy.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://navixy.com/docs/user/guide/tracking/history-view.md). # History view Access trip and event history for tracked objects. Review past routes with mileage and stops, or analyze geofence breaches, speeding, and sensor alerts. The **History** tool allows you to review and analyze past activities and events associated with your tracked objects. This feature provides a comprehensive overview of historical data, enabling you to monitor trips, stops, and other significant events, ensuring efficient fleet management and operational insights. * [Trip history](/docs/user/guide/tracking/history-view/trip-history.md)\ Review detailed records of past trips, including start and end times, distances traveled, and duration. * [Event history](/docs/user/guide/tracking/history-view/event-history.md)\ Analyze various events such as geofence breaches, speeding incidents, and sensor alerts, along with their timestamps and locations. --- # 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://navixy.com/docs/user/guide/tracking/history-view.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.