> 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/streamlog-assistant/dialog-configuration/checking-communication-between-dialog-and-the-streamlog-server.md).
# Checking communication between DiaLog and the StreamLog Server
The communications between DiaLog and the StreamLog server can be tested by running the StreamLog Connection Assistant on the PC where DiaLog is installed; once you launch the Application, you can see a diagram representing the configuration you wish to use.
Once you are ready, press, the Check DiaLog Connection button to test the Connection between the PC running DiaLog and the StreamLog Server.
The following window will be displayed.
Press the Load Security File Button to Load the “StreamLog.ssf” file.
Then select your file as follows
Then Enter the Serial Number of your Logger exactly as it is printed on the Sticker on the Device.
Now click Check Client StreamLog.
If The PC is able to simulate correct communications between DiaLog and the StreamLog Server, the following Message will be displayed.
---
# 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/streamlog-assistant/dialog-configuration/checking-communication-between-dialog-and-the-streamlog-server.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.
