Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

#

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Jump to bottom

Don't trace OPTIONS requests by default #1864

Open
sl0thentr0py opened this issue Aug 10, 2022 · 0 comments · May be fixed by #2181
Open

Don't trace OPTIONS requests by default #1864

sl0thentr0py opened this issue Aug 10, 2022 · 0 comments · May be fixed by #2181
Assignees
@sl0thentr0py
Labels
enhancement

Comments

@sl0thentr0py
Copy link
Member

sl0thentr0py commented Aug 10, 2022 •
edited by antonpirker
Loading

We decided that OPTIONS requests shouldn't be traced by default since they eat into quota a lot for some users and don't add much value.

See getsentry/sentry-javascript#5485
@sl0thentr0py sl0thentr0py self-assigned this Aug 10, 2022
@antonpirker antonpirker mentioned this issue Oct 24, 2022
Closed
@antonpirker antonpirker changed the title Don't trace OPTIONS/HEAD requests by default Don't trace OPTIONS requests by default Nov 16, 2022
@natikgadzhi natikgadzhi linked a pull request Nov 26, 2023 that will close this issue
Open
1 task
# for free to join this conversation on GitHub. Already have an account? # to comment
Assignees

@sl0thentr0py sl0thentr0py

Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Tracing: don't record HTTP OPTIONS and HEAD transactions natikgadzhi/sentry-ruby
2 participants
@sl0thentr0py @hubertdeng123