> 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/toolbar.md).
# Toolbar
The toolbar is situated at the top of the software screen and contains several key software features.
* **StreamLog—** Establishes communication with the StreamLog Server
* **StreamLog Settings—** Configuration of the communications between DiaLog and The StreamLog Server.
* **Administration—** Administration of Engineers, Vehicles and Loggers.
* **Edit Configuration—** Jumps to the ‘Configuration’ to allow changes to items logged etc.
* S**end Configuration—** Allows the Configuration to be assigned to the various Loggers.
* **Request Log Data—** Schedule Files to be downloaded.
* **Scope List—** Allows display of logged data on an Oscilloscope.
* **Reports—** Allows Logger Reports to be generated.
* **Tasks—** Allows the user to create automated transfer and alert tasks.
* **Wizards—** The wizards enable you to retrieve data and send configurations to a Logger.
* **Log Off—** This allows you to disconnect from the StreamLog Server.
---
# 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/toolbar.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.
