> For the complete documentation index, see [llms.txt](https://docs.prismacloud.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.prismacloud.io/admin-guide/32/how-to-guides/review-debug-logs.md).

# Review debug logs

Console and Defender generate logs as they run. These logs, also known as debug data, are designed to help troubleshoot operational issues. They’re different from audits, which are designed to report significant security events.

If you contact Prisma Cloud Support with an issue, you’ll be asked to collect debug data from your setup and send it to us. Debug data helps us find the root cause of problems, and provide timely resolutions.

## Collect Console debug logs

The simplest way to view Console’s debug logs is from within the UI itself. Go to **Manage > Logs > Console** and **Download Logs**.

## Collect Defender debug logs

To view Defender’s debug logs, go to **Manage > Defenders > Defenders: Deployed**. Select the Defender from the table and then click **Actions > Logs** and **Download Logs**.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.prismacloud.io/admin-guide/32/how-to-guides/review-debug-logs.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.