diff --git a/docs/concepts/data-management/filtering/index.mdx b/docs/concepts/data-management/filtering/index.mdx index 7f1a46cd2b214..b2426664c96a9 100644 --- a/docs/concepts/data-management/filtering/index.mdx +++ b/docs/concepts/data-management/filtering/index.mdx @@ -30,7 +30,7 @@ Inbound filters include: The legacy browser filters allow you to filter out certain legacy versions of browsers that are known to cause problems. -Legacy browser filters were updated in Feb 2024 and will be periodically evaluated to include additional legacy versions. +Legacy browser filters were updated in December 2025 and will be periodically evaluated to include additional legacy versions. If you had a legacy browser filter on before the update, the old filter will appear in your settings as "Deprecated". Deprecated legacy browser filters still work. However, if you turn them off, you won't be able to turn them on again and will need to use the new filters instead. @@ -49,6 +49,7 @@ Filters events based on the **originating IP address of the client making the re Sentry attempts to identify the request's origin using the **forwarded IP address**. If no forwarded IP is available, it falls back to the **direct IP** of the client connecting to Sentry's servers. The supported IP address formats are: + - **IPv4 Addresses**: Standard dotted-decimal notation (e.g., 1.2.3.4, 122.33.230.14, 127.0.0.1). - **IPv6 Addresses**: Standard colon-separated hexadecimal notation (e.g., aaaa:bbbb::cccc, a:b:c::1). - **IPv4 Network Ranges (CIDR Notation)**: IPv4 address with a subnet mask (e.g., 122.33.230.0/30, 127.0.0.0/8). @@ -133,7 +134,6 @@ The following inbound filters **do not** apply to Logs: - Request URLs - User-Agents - ## How Custom Filtering Works @@ -172,7 +172,6 @@ To use inbound data filters for log messages, keep the following in mind: - You can provide multiple patterns, one per line. The filter applies if any of the patterns match. - On logs, the filter matches the log message in the format. We do not recommend matching the full log message, and suggest you match with wildcards. For example, to match any "Connection timeout asbq33q", use the filter `*Connection timeout*`. The wildcard matcher can be used at the beginning or end of the string. - ### Glob Matching The error messages, log messages and releases filters use glob patterns. Globs are case insensitive and allow you to specify wildcards to match variable input. For example, `*panic*` matches any error that contains the words "panic", "PANIC" or "PaNiC".