> For the complete documentation index, see [llms.txt](https://docs.influxtechnology.com/support_guides/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.influxtechnology.com/support_guides/streamlog/streamlog-user-documentation/quick-start-guide/streamlog-operation/editors-tabs/fleet-overview-tab.md).
# Fleet Overview Tab
#### Fleet DTC page
Report Diagnostic Trouble Codes: By Group, By Vehicle, By Date, etc.
#### Fleet Overview page
This tab provides the complete overview of the fleet. It gives a graphical view of the numbers of connected loggers & the number of vehicles with DTC’s.
#### Fleet Distance Page
This tab provides the complete details about the distance travelled by vehicles under the fleet. It also gives a graphical representation of the same.
#### Active Vehicles Page
This tab provides the complete list of active vehicles for the specified time.
#### Fleet Parameter Page
This tab provides the statistical report of fleet parameters per vehicle.
* Users can select any measurement item to be monitored continuously.
* Sampled results are shown from the data compiled across the fleet.
* Key parameters can be linked across different modules.
{% hint style="info" %}
#### Notes:
* This feature requires additional purchases. Please contact Influx Sales.
{% endhint %}
---
# 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.influxtechnology.com/support_guides/streamlog/streamlog-user-documentation/quick-start-guide/streamlog-operation/editors-tabs/fleet-overview-tab.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.
