> For the complete documentation index, see [llms.txt](https://docs.elastiflow.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.elastiflow.com/trapcoll/configuration/processing-traps/processor.md).

# Processor configuration options

#### EF\_PROCESSOR\_TRAP\_DSL\_ENABLE

Set this to `false` to disable trap DSL processing. Traps will be collected and normalized, but not processed via the DSL.

* Valid Values
  * `true`, `false`
* Default
  * `true`

#### EF\_PROCESSOR\_TRAP\_DSL\_ENUM\_DEFINITIONS\_DIRECTORY\_PATH

The DSL Processor also supports enumerations for enrichment, which are used to define a set of constants that can be used in rules. Enumerations are defined in a set of files and are used to define a set of constants that can be used in rules.

* Default
  * `/etc/elastiflow/snmp/enums`

#### EF\_PROCESSOR\_TRAP\_DSL\_RULES\_DIRECTORY\_PATH

The DSL Processor is powered by a set of rules that are defined in a set of files. Each rule is defined in a separate file and is composed of a set of conditions and actions. The conditions are used to filter incoming traps, while the actions are used to transform and enrich the traps.

* Default
  * `/etc/elastiflow/snmp/traps/rules`

#### EF\_PROCESSOR\_TRAP\_DSL\_GENERIC\_FILE\_PATH

The Generic file is used to load rules for generic traps.

* Default
  * `/etc/elastiflow/snmp/traps/generic.yml`

#### EF\_PROCESSOR\_TRAP\_DSL\_ENTERPRISE\_FILE\_PATH

The Enterprise file is used as a mapping between Enterprise OIDs and rules files. The enterprise OIDs are used to identify the vendor of the trap.

* Default
  * `/etc/elastiflow/snmp/traps/enterprises.yml`

#### More Options

For more process configuration options, see our list of [common processor options](/trapcoll/configuration/processing-traps/traps-processing-functions.md)


---

# 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.elastiflow.com/trapcoll/configuration/processing-traps/processor.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.