> 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/sessions-tab.md).
# Sessions Tab
Allows recorded Data to be visualised, deleted and saved for further analysis.
#### Extract Stream Data
It is possible to import the data into a DiaLog oscilloscope for more detailed data analysis and export.
Select the IVD file you wish to look at and click extract stream data.
This will load the recorded ‘Stream Data’ into a DiaLog oscilloscope. Depending on the size of the data log, this process may take a little while—a progress window is displayed.
Once the data has loaded, the oscilloscope will be shown.
Once the scope has been loaded, it will remain accessible in StreamLog and DiaLog via either the ‘Scope List’ or ‘Show Scope’ toolbar icons. This allows ‘Stream Data’ logs to be loaded to DiaLog scopes and accessed via DiaLog after StreamLog has been closed. This gives the user access to the complete DiaLog scope functionality, including data export options. Full details can be found in the DiaLog documentation.
---
# 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/sessions-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.
