> 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/software-introduction/editors-tabs.md).
# Editors Tabs
The ‘Editors’ tabs allow the user to navigate amongst the main features in StreamLog for the selected item in the ‘Projects’ panel.
* **Sessions—** The tab provides information regarding the active and previous data logging sessions from the Logger.
* **Loggers—** The tab provides information regarding the loggers assigned to the configuration.
* **Vehicles—** The tab provides information regarding the events that have occurred during data logging.
* **Engineers—** The tab provides information regarding the engineers assigned to a project/configuration.
* **Live View—** The tab allows you to view the live data from the Logger.
* **Fleet Overview—** Tab provides statistical information related to various fleet parameters.
* **Data Management—** Tab provides information regarding IVD files created in the Logger.
* **Fleet Reports—** The tab allows users to create advanced reports using fleet parameter data.
---
# 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/software-introduction/editors-tabs.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.
