Skip to content

Commit 16404bc

Browse files
mydeabitsandfoxes
authored andcommitted
fix(js): Update denyUrls text in filtering page (#13494)
Clarify that `denyUrl` applies to stack frame origin, not the page that an error comes from.
1 parent ca43e20 commit 16404bc

File tree

1 file changed

+4
-1
lines changed

1 file changed

+4
-1
lines changed

docs/platforms/javascript/common/configuration/filtering.mdx

+4-1
Original file line numberDiff line numberDiff line change
@@ -32,14 +32,17 @@ See <PlatformLink to="/configuration/options/#beforeSend">beforeSend</PlatformLi
3232

3333
### Using `allowUrls` and `denyUrls`
3434

35-
You can construct an allowed list of domains for errors. Only errors created within these domains will be captured. For example, if your scripts are loaded from `cdn.example.com` and your site is `example.com`, you can set `allowUrls` to:
35+
You can configure the SDK to avoid sending errors that originate in scripts from certain domains.
36+
For example, if your scripts are loaded from `cdn.example.com` and your site is `example.com`, you can can configure `allowUrls` as follows to avoid capturing errors from other domains:
3637

3738
```javascript
3839
Sentry.init({
3940
allowUrls: [/https?:\/\/((cdn|www)\.)?example\.com/],
4041
});
4142
```
4243

44+
Note that this filters errors based on their stack frames, not the URL of the page where the error occurred.
45+
4346
You can also use `denyUrls` if you want to block errors created on specific URLs from being sent to Sentry.
4447

4548
- See <PlatformLink to="/configuration/options/#allowUrls">allowUrls</PlatformLink> details

0 commit comments

Comments
 (0)