> 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/cortex-cloud-runtime-security/cortex-cloud-data-sources-and-connectors/generic-on-premise-data-collectors/xdr-collectors/xdr-collector-datasets.md).

# XDR Collector datasets

After Cortex Cloud begins receiving data from your XDR Collectors configuration, the app automatically creates an XQL dataset.

After Cortex Cloud begins receiving data from your XDR Collectors configuration that are dedicated for on-premises data collection on Windows and Linux machines.

* For Filebeat, the app automatically creates an Cortex Query Language (XQL) dataset of event logs using the vendor name and the product name specified in the configuration file section of the Filebeat profile. The dataset name follows the format `<vendor>_<product>_raw`. If not specified, Cortex Cloud automatically creates a new default dataset in the format `<module>_<module>_raw` or `<input>_<input>_raw`. For example, if you are using the NGINX module, the dataset is called `nginx_nginx_raw`.
* For Winlogbeat, the app automatically creates an XQL dataset of event logs using the vendor name and the product name specified in the configuration file section of the Winlogbeat profile. The dataset name follows the format `<vendor>_<product>_raw`. If not specified, Cortex Cloud automatically creates a new default dataset, `microsoft_windows_raw`, for event log collection. Winlogbeat data is also normalized to `xdr_data` (and thus the `xdr_event_log` preset).

After Cortex Cloud creates the dataset, you can search for your XDR Collector data using XQL Search.


---

# 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://cortex-docs.paloaltonetworks.com/cortex-cloud-runtime-security/cortex-cloud-data-sources-and-connectors/generic-on-premise-data-collectors/xdr-collectors/xdr-collector-datasets.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.