You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/concepts/data-management/filtering/index.mdx
+31Lines changed: 31 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -110,6 +110,29 @@ Once applied, you can track the filtered events (numbers and cause) using the gr
110
110
111
111

112
112
113
+
## Logs Filtering
114
+
115
+
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.
116
+
117
+
The following inbound filters **do** apply to Logs:
118
+
119
+
-**Log Message** - Filters logs based on the log message match
120
+
-**Releases** - Filters replays from specific release versions
121
+
122
+
The following inbound filters **do not** apply to Session Replays:
@@ -135,6 +158,14 @@ To filter releases, keep the following in mind:
135
158
- Globbing rules apply and there is no special casing for SemVer. This allows for matching prefixes, such as `my-example@1.*`.
136
159
- The filter never applies to events without a release.
137
160
161
+
### Log Message
162
+
163
+
To use inbound data filters for log messages, keep the following in mind:
164
+
165
+
- You can provide multiple patterns, one per line. The filter applies if any of the patterns match.
166
+
- 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.
167
+
168
+
138
169
### Glob Matching
139
170
140
171
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".
0 commit comments