Adding docs for Log Inbound filters (#14584)

<!-- Use this checklist to make sure your PR is ready for merge. You may
delete any sections you don't need. -->

## DESCRIBE YOUR PR
*Tell us what you're changing and why. If your PR **resolves an issue**,
please link it so it closes automatically.*

## IS YOUR CHANGE URGENT?  

Help us prioritize incoming PRs by letting us know when the change needs
to go live.
- [ ] Urgent deadline (GA date, etc.): <!-- ENTER DATE HERE -->
- [ ] Other deadline: <!-- ENTER DATE HERE -->
- [ ] None: Not urgent, can wait up to 1 week+

## SLA

- Teamwork makes the dream work, so please add a reviewer to your PRs.
- Please give the docs team up to 1 week to review your PR unless you've
added an urgent due date to it.
Thanks in advance for your help!

## PRE-MERGE CHECKLIST

*Make sure you've checked the following before merging your changes:*

- [ ] Checked Vercel preview for correctness, including links
- [ ] PR was reviewed and approved by any necessary SMEs (subject matter
experts)
- [ ] PR was reviewed and approved by a member of the [Sentry docs
team](https://github.com/orgs/getsentry/teams/docs)

## LEGAL BOILERPLATE

<!-- Sentry employees and contractors can delete or ignore this section.
-->

Look, I get it. The entity doing business as "Sentry" was incorporated
in the State of Delaware in 2015 as Functional Software, Inc. and is
gonna need some rights from me in order to utilize my contributions in
this here PR. So here's the deal: I retain all rights, title and
interest in and to my contributions, and by keeping this boilerplate
intact I confirm that Sentry can use, modify, copy, and redistribute my
contributions, under Sentry's choice of terms.

## EXTRA RESOURCES

- [Sentry Docs contributor guide](https://docs.sentry.io/contributing/)

---------

Co-authored-by: Tony Xiao <[email protected]>

Author: Dhrumil-Sentry

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 Logs.
+
+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 Logs:
+
+- 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,9 +158,17 @@ 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".
+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".
 
 Some symbols, such as the `*` character, receive special meaning as meta characters. To match a literal asterisk, escape it with a backslash: `\*`. Inbound data filters use the following meta characters: