> 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-xsiam/configure-cortex-xsiam/data-management/parsing-rules/parsing-rules-file-structure-and-syntax/ingest/fields.md).

# fields

### Syntax

```
[INGEST: vendor="<vendor>", product="<product>", target_dataset="<dataset_name>"]
fields <field_1>, <field_2>, ... ;
```

### Description

The `fields` stage in the `INGEST` section of a parsing rule allows you to explicitly define which fields from a raw log should be saved into a dataset.

This stage works identically to the [fields](https://cortex-docs.paloaltonetworks.com/xql-command-reference-guide/readme/stages/fields) stage in XQL, which defines the columns returned in a query result set. Yet, when used within the `INGEST` section of a parsing rule, it serves to control the schema of the stored data.

#### **Usage**

Use the `fields` stage to:

* **Resume data flow:** If a dataset has reached its 2,000-field limit, you can use the `fields` stage to explicitly select only the necessary fields, allowing automatic parsing to continue.
* **Manage large datasets:** If you know in advance that a data source will ingest more than 2,000 fields, you can use this stage to pre-filter and define the specific fields you wish to retain.

{% hint style="info" %}
**Note**

For more details on field selection, including how to use aliases and wildcards, see the Cortex Query Language (XQL) [fields](https://cortex-docs.paloaltonetworks.com/xql-command-reference-guide/readme/stages/fields) stage reference.
{% 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 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-xsiam/configure-cortex-xsiam/data-management/parsing-rules/parsing-rules-file-structure-and-syntax/ingest/fields.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.