Skip to content

Commit 7222a0b

Browse files
Make it clear that dsn needs to be set when using tunnel (#8337)
Co-authored-by: Shana Matthews <[email protected]>
1 parent e96655d commit 7222a0b

File tree

1 file changed

+1
-2
lines changed

1 file changed

+1
-2
lines changed

src/platforms/common/configuration/options.mdx

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -174,8 +174,7 @@ By default the SDK will try to read this value from the `SENTRY_ENVIRONMENT` env
174174

175175
<ConfigKey name="tunnel" supported={["javascript", "node"]} notSupported={["react-native"]}>
176176

177-
Sets the URL that will be used to transport captured events, instead of using the DSN. This can be used to work around ad-blockers or to have more granular
178-
control over events sent to Sentry. This option **requires the implementation** of a custom server endpoint. Learn more and find examples in [Dealing with Ad-Blockers](/platforms/javascript/troubleshooting/#dealing-with-ad-blockers).
177+
Sets the URL that will be used to transport captured events. This can be used to work around ad-blockers or to have more granular control over events sent to Sentry. Adding your DSN is still required when using this option so necessary attributes can be set on the generated Sentry data. This option **requires the implementation** of a custom server endpoint. Learn more and find examples in [Dealing with Ad-Blockers](/platforms/javascript/troubleshooting/#dealing-with-ad-blockers).
179178

180179
</ConfigKey>
181180

0 commit comments

Comments
 (0)