> 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/flowcoll/configuration/enrichment-options/enrich_apps.md).

# Application ID

NetObserv Flow will cache application attributes learned from option data. It also allows users to define application attributes by any combination of IP/CIDR/IP range and port/port range.

## EF\_PROCESSOR\_ENRICH\_APP\_ID\_ENABLE

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

## EF\_PROCESSOR\_ENRICH\_APP\_ID\_PATH

If vendor-defined AppID to application attribute mappings is enabled (`EF_PROCESSOR_ENRICH_APP_ID_ENABLE` is `true`) this setting specifies the path to the file.

* Default
  * `/etc/elastiflow/app/appid.yml`

## EF\_PROCESSOR\_ENRICH\_APP\_ID\_TTL

The length of time the application attributes will be cached after they are initially fetched.

{% hint style="info" %}
Changes to the underlying files will not be picked up, even after the files have been re-loaded at the refresh interval, until the AppID has expired from the cache.
{% endhint %}

* Default
  * `7200`

## EF\_PROCESSOR\_ENRICH\_APP\_IPPORT\_ENABLE

While various flow record sources send the mapping of application IDs to application names as option data, in cases where no application identity technology is available, applications can be statically specified by IP address and port number.

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

## EF\_PROCESSOR\_ENRICH\_APP\_IPPORT\_PATH

If user-defined IP/port to application mappings is enabled (`EF_PROCESSOR_ENRICH_APP_IPPORT_ENABLE` is `true`), this setting specifies the path to this file.

An example of the format of this file is:

```yaml
192.168.1.0/24:
  8090:
    name: "Synergy-cidr-port"
    category: "category-cidr-port"
    subcategory: "subcategory-cidr-port"
    metadata:
      ".location": "austin-cidr-port"
      "business.unit": "finance-cidr-port"
      "dev.unit": "dev-cidr-port"
      "app.count": 27

192.168.1.1-192.168.1.20:
  8090:
    name: "Synergy-iprange-port"
    category: "category-iprange-port"
    subcategory: "subcategory-iprange-port"
    metadata:
      .location: "austin-iprange-port"

  8090-9000:
    name: "Synergy-iprange-portrange"
    category: "category-iprange-portrange"
    subcategory: "subcategory-iprange-portrange"
    metadata:
      .location: "austin-iprange-portrange"
      business.unit: "finance-iprange-portrange"
      qa.unit: "qa-iprange-portrange"
      finance.unit: "finance-iprange-portrange"

192.168.1.1:
  8090:
    name: "Synergy-ip-port"
    category: "category-ip-port"
    subcategory: "subcategory-ip-port"
    metadata:
      .location: "austin-ip-port"
      business.unit: "finance-ip-port"
```

* Default
  * `/etc/elastiflow/app/ipport.yml`

## EF\_PROCESSOR\_ENRICH\_APP\_IPPORT\_TTL

The length of time the application attributes will be cached after they are initially fetched.

{% hint style="info" %}
Changes to the underlying files will not be picked up, even after the files have been re-loaded at the refresh interval, until the IP/Port has expired from the cache.
{% endhint %}

* Default
  * `7200`

## EF\_PROCESSOR\_ENRICH\_APP\_IPPORT\_PRIVATE

If user-defined application attributes are enabled (`EF_PROCESSOR_ENRICH_APP_IPPORT_ENABLE` is `true`) this option specifies whether application names will be checked for private IP addresses.

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

## EF\_PROCESSOR\_ENRICH\_APP\_IPPORT\_PUBLIC

If user-defined application attributes are enabled (`EF_PROCESSOR_ENRICH_APP_IPPORT_ENABLE` is `true`) this option specifies whether application names will be checked for public IP addresses.

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

## EF\_PROCESSOR\_ENRICH\_APP\_REFRESH\_RATE

The files defined for application attribute enrichment can be loaded automatically to refresh values without restarting the collector. This value specifies the refresh interval, in minutes, that the file will be reloaded. The value of `0` disables refreshing of the values.

* Default
  * `15`


---

# 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.elastiflow.com/flowcoll/configuration/enrichment-options/enrich_apps.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.