Skip to content

Adding docs for Log Inbound filters #14584

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
Dhrumil-Sentry merged 4 commits into from
Aug 7, 2025
Merged

Adding docs for Log Inbound filters #14584

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
0a7d5c8
Log Inbound filters
Dhrumil-Sentry Aug 7, 2025
88f60fd
Update docs/concepts/data-management/filtering/index.mdx
Dhrumil-Sentry Aug 7, 2025
8d2a46f
Update docs/concepts/data-management/filtering/index.mdx
Dhrumil-Sentry Aug 7, 2025
3603a6c
Minor edit to glob pattern
Dhrumil-Sentry Aug 7, 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
33 changes: 32 additions & 1 deletion docs/concepts/data-management/filtering/index.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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" />
Expand All @@ -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.
Copy link
Member

@Zylphrex Zylphrex Aug 7, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Might be good to mention that log message uses glob patterns in the Glob Matching section below.



### 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:

Expand Down