> 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/33/audit/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 are different from audits, which are designed to report significant security events. If you contact Prisma Cloud Support with an issue, you will 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 **Manage > Logs > Console** and **Download Logs**. ### Send Debug Logs to Syslog You can also send console logs directly to a syslog server. This can be an efficient way to manage logs, especially when consolidating data for analysis. * Secure Transmission with TLS Certificate: If you provide a TLS certificate on **Manage > Alerts > Logging** and **Syslog** is set to **Enabled**, the logs will be sent securely over HTTPS, ensuring that your data is encrypted during transit and protected from unauthorized access. See [Sending syslog messages to a network endpoint](/admin-guide/33/audit/logging.md) for more information. * Standard Transmission without TLS Certificate: Without a TLS certificate, the logs will be sent over HTTP, which is not secured. This method is faster but does not encrypt the data. ## Collect Defender debug logs To view debug logs of Defender , access **Manage > Defenders > Deployed Defenders**. Select the Defender from the table and then select **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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.prismacloud.io/admin-guide/33/audit/review-debug-logs.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.