> 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.md). # Quick Start Guide This section outlines the main steps required to be completed to use StreamLog successfully. It is not intended as a complete user guide but rather to inform the user of the main steps to set up and operate a successful StreamLog system. Detailed instructions for each item can be found in the relevant sections highlighted below. * **DiaLog configuration—**This step is required to step up DiaLog to utilise and access the StreamLog server. * **Accessing StreamLog—**Once DiaLog has been configured, open DiaLog and ensure your PC has a good internet connection established. Access to StreamLog is via the dedicated toolbar icon. You will be required to select an engineer to sign in. * **Project set up—**Within StreamLog, you need to create a ‘Project’ and assign the required Rebel data loggers to this project. * **Rebel alignment—**Once StreamLog has been set up, the Rebel data logger(s) to be used must be aligned with the StreamLog server. This requires configuring the Rebel GPRS settings to match the SIM card service provider and StreamLog server. * **Stream Data—**The key data items to be streamed to the server must then be selected. This is performed in DiaLog. * **Vehicle Structure upload—**The final step is to upload the Vehicle Structure to the Rebel data logger and the StreamLog server. * **Create Fleet Report—**How to create fleet reports by creating fleet parameters. --- # 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.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.