Skip to content

doc(proguard): No inbound filters #15543

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
merged 2 commits into from
Nov 19, 2025
Merged

doc(proguard): No inbound filters #15543

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
3eb23b3
doc(proguard): No inbound filters
jjbayer Nov 18, 2025
9d74ea9
Apply suggestion from @jjbayer
jjbayer Nov 18, 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
6 changes: 6 additions & 0 deletions docs/concepts/data-management/filtering/index.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -151,6 +151,12 @@ To use inbound data filters for error messages, keep the following in mind:

To ensure you're adding the correct message to the inbound filter setting, check the JSON for an event in the issue. The filter by error message setting matches the data found in the "title" field near the end of the file.

<Alert title="Note" level="warning">

Matching on the deobfuscated `{exception.type}` is not supported for <PlatformLink to="/enhance-errors/proguard/">ProGuard</PlatformLink> events, because deobfuscation of class names happens after ingestion.

</Alert>

### Releases

To filter releases, keep the following in mind:
Expand Down
Loading