Skip to content

[Docs] Add applies_to to DNS processor docs #45580

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
vishaangelova merged 3 commits into from
Jul 28, 2025
Merged

[Docs] Add applies_to to DNS processor docs #45580

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
18ebcc5
Add applies_to to DNS processor docs
vishaangelova Jul 28, 2025
acb4ac0
Apply suggestions from code review
vishaangelova Jul 28, 2025
665db9c
Merge branch 'main' into add-applies-to-tags-dns
vishaangelova Jul 28, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions docs/reference/auditbeat/processor-dns.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -81,8 +81,8 @@ The `dns` processor has the following configuration settings:
`success_cache.min_ttl`
: The duration of the minimum alternative cache TTL for successful DNS responses. Ensures that `TTL=0` successful reverse DNS responses can be cached. Valid time units are "ns", "us" (or "µs"), "ms", "s", "m", "h". Default value is `1m`.

`success_cache.enabled`
: Whether the success cache should be enabled. The default value is `true`, meaning the cache is used by default.
`success_cache.enabled` {applies_to}`stack: ga 9.1.0`
: Whether the success cache should be enabled. The default value is `true`, meaning the cache is used by default.

::::{note}
Disabling the cache has throughput implications, requiring each event to perform a round trip to the DNS server. For example, if a DNS lookup takes 1 ms, serial throughput is limited to a maximum of 1,000 events per second.
Expand All @@ -97,8 +97,8 @@ Disabling the cache has throughput implications, requiring each event to perform
`failure_cache.ttl`
: The duration for which failures are cached. Valid time units are "ns", "us" (or "µs"), "ms", "s", "m", "h". Default value is `1m`.

`failure_cache.enabled`
: Whether the failure cache should be enabled. The default value is `true`, meaning the cache is used by default.
`failure_cache.enabled` {applies_to}`stack: ga 9.1.0`
: Whether the failure cache should be enabled. The default value is `true`, meaning the cache is used by default.

::::{note}
Disabling the cache has throughput implications, requiring each event to perform a round trip to the DNS server. For example, if a DNS lookup takes 1 ms, serial throughput is limited to a maximum of 1,000 events per second. Additionally, if the failure occurs because the server is overloaded, retrying immediately might have compounding effects.
Expand Down
8 changes: 4 additions & 4 deletions docs/reference/filebeat/processor-dns.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -81,8 +81,8 @@ The `dns` processor has the following configuration settings:
`success_cache.min_ttl`
: The duration of the minimum alternative cache TTL for successful DNS responses. Ensures that `TTL=0` successful reverse DNS responses can be cached. Valid time units are "ns", "us" (or "µs"), "ms", "s", "m", "h". Default value is `1m`.

`success_cache.enabled`
: Whether the success cache should be enabled. The default value is `true`, meaning the cache is used by default.
`success_cache.enabled` {applies_to}`stack: ga 9.1.0`
: Whether the success cache should be enabled. The default value is `true`, meaning the cache is used by default.

::::{note}
Disabling the cache has throughput implications, requiring each event to perform a round trip to the DNS server. For example, if a DNS lookup takes 1 ms, serial throughput is limited to a maximum of 1,000 events per second.
Expand All @@ -97,8 +97,8 @@ Disabling the cache has throughput implications, requiring each event to perform
`failure_cache.ttl`
: The duration for which failures are cached. Valid time units are "ns", "us" (or "µs"), "ms", "s", "m", "h". Default value is `1m`.

`failure_cache.enabled`
: Whether the failure cache should be enabled. The default value is `true`, meaning the cache is used by default.
`failure_cache.enabled` {applies_to}`stack: ga 9.1.0`
: Whether the failure cache should be enabled. The default value is `true`, meaning the cache is used by default.

::::{note}
Disabling the cache has throughput implications, requiring each event to perform a round trip to the DNS server. For example, if a DNS lookup takes 1 ms, serial throughput is limited to a maximum of 1,000 events per second. Additionally, if the failure occurs because the server is overloaded, retrying immediately might have compounding effects.
Expand Down
8 changes: 4 additions & 4 deletions docs/reference/heartbeat/processor-dns.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -81,8 +81,8 @@ The `dns` processor has the following configuration settings:
`success_cache.min_ttl`
: The duration of the minimum alternative cache TTL for successful DNS responses. Ensures that `TTL=0` successful reverse DNS responses can be cached. Valid time units are "ns", "us" (or "µs"), "ms", "s", "m", "h". Default value is `1m`.

`success_cache.enabled`
: Whether the success cache should be enabled. The default value is `true`, meaning the cache is used by default.
`success_cache.enabled` {applies_to}`stack: ga 9.1.0`
: Whether the success cache should be enabled. The default value is `true`, meaning the cache is used by default.

::::{note}
Disabling the cache has throughput implications, requiring each event to perform a round trip to the DNS server. For example, if a DNS lookup takes 1 ms, serial throughput is limited to a maximum of 1,000 events per second.
Expand All @@ -97,8 +97,8 @@ Disabling the cache has throughput implications, requiring each event to perform
`failure_cache.ttl`
: The duration for which failures are cached. Valid time units are "ns", "us" (or "µs"), "ms", "s", "m", "h". Default value is `1m`.

`failure_cache.enabled`
: Whether the failure cache should be enabled. The default value is `true`, meaning the cache is used by default.
`failure_cache.enabled` {applies_to}`stack: ga 9.1.0`
: Whether the failure cache should be enabled. The default value is `true`, meaning the cache is used by default.

::::{note}
Disabling the cache has throughput implications, requiring each event to perform a round trip to the DNS server. For example, if a DNS lookup takes 1 ms, serial throughput is limited to a maximum of 1,000 events per second. Additionally, if the failure occurs because the server is overloaded, retrying immediately might have compounding effects.
Expand Down
8 changes: 4 additions & 4 deletions docs/reference/metricbeat/processor-dns.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -81,8 +81,8 @@ The `dns` processor has the following configuration settings:
`success_cache.min_ttl`
: The duration of the minimum alternative cache TTL for successful DNS responses. Ensures that `TTL=0` successful reverse DNS responses can be cached. Valid time units are "ns", "us" (or "µs"), "ms", "s", "m", "h". Default value is `1m`.

`success_cache.enabled`
: Whether the success cache should be enabled. The default value is `true`, meaning the cache is used by default.
`success_cache.enabled` {applies_to}`stack: ga 9.1.0`
: Whether the success cache should be enabled. The default value is `true`, meaning the cache is used by default.

::::{note}
Disabling the cache has throughput implications, requiring each event to perform a round trip to the DNS server. For example, if a DNS lookup takes 1 ms, serial throughput is limited to a maximum of 1,000 events per second.
Expand All @@ -97,8 +97,8 @@ Disabling the cache has throughput implications, requiring each event to perform
`failure_cache.ttl`
: The duration for which failures are cached. Valid time units are "ns", "us" (or "µs"), "ms", "s", "m", "h". Default value is `1m`.

`failure_cache.enabled`
: Whether the failure cache should be enabled. The default value is `true`, meaning the cache is used by default.
`failure_cache.enabled` {applies_to}`stack: ga 9.1.0`
: Whether the failure cache should be enabled. The default value is `true`, meaning the cache is used by default.

::::{note}
Disabling the cache has throughput implications, requiring each event to perform a round trip to the DNS server. For example, if a DNS lookup takes 1 ms, serial throughput is limited to a maximum of 1,000 events per second. Additionally, if the failure occurs because the server is overloaded, retrying immediately might have compounding effects.
Expand Down
8 changes: 4 additions & 4 deletions docs/reference/packetbeat/processor-dns.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -81,8 +81,8 @@ The `dns` processor has the following configuration settings:
`success_cache.min_ttl`
: The duration of the minimum alternative cache TTL for successful DNS responses. Ensures that `TTL=0` successful reverse DNS responses can be cached. Valid time units are "ns", "us" (or "µs"), "ms", "s", "m", "h". Default value is `1m`.

`success_cache.enabled`
: Whether the success cache should be enabled. The default value is `true`, meaning the cache is used by default.
`success_cache.enabled` {applies_to}`stack: ga 9.1.0`
: Whether the success cache should be enabled. The default value is `true`, meaning the cache is used by default.

::::{note}
Disabling the cache has throughput implications, requiring each event to perform a round trip to the DNS server. For example, if a DNS lookup takes 1 ms, serial throughput is limited to a maximum of 1,000 events per second.
Expand All @@ -97,8 +97,8 @@ Disabling the cache has throughput implications, requiring each event to perform
`failure_cache.ttl`
: The duration for which failures are cached. Valid time units are "ns", "us" (or "µs"), "ms", "s", "m", "h". Default value is `1m`.

`failure_cache.enabled`
: Whether the failure cache should be enabled. The default value is `true`, meaning the cache is used by default.
`failure_cache.enabled` {applies_to}`stack: ga 9.1.0`
: Whether the failure cache should be enabled. The default value is `true`, meaning the cache is used by default.

::::{note}
Disabling the cache has throughput implications, requiring each event to perform a round trip to the DNS server. For example, if a DNS lookup takes 1 ms, serial throughput is limited to a maximum of 1,000 events per second. Additionally, if the failure occurs because the server is overloaded, retrying immediately might have compounding effects.
Expand Down
8 changes: 4 additions & 4 deletions docs/reference/winlogbeat/processor-dns.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -81,8 +81,8 @@ The `dns` processor has the following configuration settings:
`success_cache.min_ttl`
: The duration of the minimum alternative cache TTL for successful DNS responses. Ensures that `TTL=0` successful reverse DNS responses can be cached. Valid time units are "ns", "us" (or "µs"), "ms", "s", "m", "h". Default value is `1m`.

`success_cache.enabled`
: Whether the success cache should be enabled. The default value is `true`, meaning the cache is used by default.
`success_cache.enabled` {applies_to}`stack: ga 9.1.0`
: Whether the success cache should be enabled. The default value is `true`, meaning the cache is used by default.

::::{note}
Disabling the cache has throughput implications, requiring each event to perform a round trip to the DNS server. For example, if a DNS lookup takes 1 ms, serial throughput is limited to a maximum of 1,000 events per second.
Expand All @@ -97,8 +97,8 @@ Disabling the cache has throughput implications, requiring each event to perform
`failure_cache.ttl`
: The duration for which failures are cached. Valid time units are "ns", "us" (or "µs"), "ms", "s", "m", "h". Default value is `1m`.

`failure_cache.enabled`
: Whether the failure cache should be enabled. The default value is `true`, meaning the cache is used by default.
`failure_cache.enabled` {applies_to}`stack: ga 9.1.0`
: Whether the failure cache should be enabled. The default value is `true`, meaning the cache is used by default.

::::{note}
Disabling the cache has throughput implications, requiring each event to perform a round trip to the DNS server. For example, if a DNS lookup takes 1 ms, serial throughput is limited to a maximum of 1,000 events per second. Additionally, if the failure occurs because the server is overloaded, retrying immediately might have compounding effects.
Expand Down
Loading