> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/data-security-documentation/data-management/broker-vm/manage-broker-vm/collect-broker-vm-logs.md).

# Collect Broker VM Logs

Learn more about collecting logs from a Broker VM to review them as part of an investigation.

Cortex Data Security enables you to collect your Broker VM logs directly from the Cortex Data Security management console.

You can collect logs by either regenerating the most up-to-date logs and downloading them once they are ready, or downloading the current logs from the last creation date reflected in the TIMESTAMP.

1. Select Settings → Configurations → Data Broker → Broker VMs to view the Broker VMs table in the Brokers tab.
2. Locate your Broker VM, right-click and select either Generate New Logs or Download Logs ().

{% hint style="info" %}

#### Note

The Download Logs () is only displayed when you’ve downloaded your logs previously using Generate New Logs. Logs are generated automatically, but can take up to a few minutes depending on the size of the logs.
{% endhint %}


---

# 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://cortex-docs.paloaltonetworks.com/data-security-documentation/data-management/broker-vm/manage-broker-vm/collect-broker-vm-logs.md?ask=<question>&goal=<user_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.