Skip to content
For the complete documentation index, see llms.txt. This page is also available as Markdown.

When will changes to IP address user defined metadata (UDM) or DNS be available

For both User Defined Metadata and DNS enrichment, there are several refresh settings and cache timings that need to be considered to determine the time in which a change should be visible.

In both cases, the cache lifetime is controlled by the EF_PROCESSOR_ENRICH_IPADDR_TTL setting.

User Defined Metadata (UDM)

The following settings can impact the time for changes in UDM to take effect:

  1. (for file based changes) Metadata refresh rate: EF_PROCESSOR_ENRICH_IPADDR_METADATA_REFRESH_RATE

  2. IP address enrichment cache time to live: EF_PROCESSOR_ENRICH_IPADDR_TTL

File based changes can take up to the sum of these two settings before they are seen in the data. API changes will update the in-memory value immediately, so it will take up to the cache TTL value before the changes are seen.

DNS enrichment

The following settings can impact the time for changes in DNS enrichment to take effect:

  1. User defined DNS mapping refresh rate: EF_PROCESSOR_ENRICH_IPADDR_DNS_USERDEF_REFRESH_RATE

  2. Include / Exclude file refresh rate: EF_PROCESSOR_ENRICH_IPADDR_DNS_INCLEXCL_REFRESH_RATE

  3. IP address enrichment cache time to live: EF_PROCESSOR_ENRICH_IPADDR_TTL

File based DNS changes will take up to the sum of their respective refresh rate and the IP address cache TTL before they are seen.

Changes in an external DNS system will take up to the time for the change to propagate to the DNS server used by the collector plus the IP address cache TTL before they are seen.

Last updated

Was this helpful?