Adding docs for Log Inbound filters

docs/concepts/data-management/filtering/index.mdx

@@ -110,6 +110,29 @@ Once applied, you can track the filtered events (numbers and cause) using the gr
 
 ![](./img/builtin-inbound-filters.png)
 
+## Logs Filtering
+
+Inbound data filters have partial support for [Logs](https://docs.sentry.io/product/explore/logs/). Only a subset of the available inbound filters apply to Session Replays.
+
+The following inbound filters **do** apply to Logs:
+
+- **Log Message** - Filters logs based on the log message match
+- **Releases** - Filters replays from specific release versions
+
+The following inbound filters **do not** apply to Session Replays:
+
+- Error messages
+- Browser extension errors  
+- Web crawler errors
+- Legacy browser filters
+- React hydration errors
+- ChunkLoadErrors
+- Health check transactions
+- IP Address
+- Request URLs
+- User-Agents
+
+
 ## How Custom Filtering Works
 
 <Include name="feature-available-for-plan-trial-business.mdx" />
@@ -135,6 +158,14 @@ To filter releases, keep the following in mind:
 - Globbing rules apply and there is no special casing for SemVer. This allows for matching prefixes, such as `my-example@1.*`.
 - The filter never applies to events without a release.
 
+### Log Message
+
+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 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".