> For the complete documentation index, see [llms.txt](https://docs.couchdrop.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.couchdrop.io/storage/local-storage/logging-and-debugging.md). # Logging and Debugging Learn about logging and debugging with regards to Windows file servers The Couchdrop Windows Agent creates log files that can help diagnose connection, configuration, and transfer issues. The Couchdrop support team may also ask you to provide these logs when investigating an issue. ## How to find Couchdrop Agent logs in Windows By default, the Couchdrop Agent stores its logs in: ``` C:\Users\%username%\AppData\Local\CouchdropCloudConnector ``` The logs are stored alongside the agent's local configuration files. ## How to view logs from the Couchdrop Agent You can also access the logs directly from the Couchdrop Agent. Open the **Settings** menu using the gear icon. From there, you can use the available shortcuts to open the local log directory and configuration files. If you are working with Couchdrop support, provide the requested log files from this location to help with debugging. --- # 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.couchdrop.io/storage/local-storage/logging-and-debugging.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.