> For the complete documentation index, see [llms.txt](https://docs.sprinto.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sprinto.com/monitors/dr.-sprinto-and-manual-inputs/how-do-you-copy-the-debug-report-for-dr.-sprinto.md).
# How do you copy the debug report for Dr. Sprinto
The following guide helps you to get the debug report from the installed Dr. Sprinto app on your computer.
A debug report typically consists of database operations, system processes, and encountered errors during the tasks. This debug report helps us understand the issue better and provide a viable solution quickly.
Below are the procedures for getting a debug report based on the operating system you are using:
**Windows**:
1. Go to the Windows taskbar and navigate to the installed Dr. Sprinto app.
2. **Right-click** the Dr. Sprinto app, and navigate to **Help** > **Copy Debug info**.\
**Note**: The Debug log gets copied to your clipboard.
**Mac**:
1. Open the Dr. Sprinto app and hover over the top bar to the Dr. Sprinto icon.
2. **Right-click** the Dr. Sprinto icon from the top bar, then navigate to **Help** > **Copy Debug Info**.\
**Note**: The Debug log gets copied to your clipboard.
Paste the copied debug report in the email and send it to [Sprinto support](mailto:www.support@Sprinto.com).
---
# 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.sprinto.com/monitors/dr.-sprinto-and-manual-inputs/how-do-you-copy-the-debug-report-for-dr.-sprinto.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.
