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
Make sure that frameworks based on WSGI do not create transactions for the HTTP methods OPTIONS and HEAD by default.
For Django and Flask also add a config option to the integrations to specify which HTTP methods to create transactions for.
(For other smaller frameworks we keep the default of not creating OPTIONS and HEAD transaction, but will add an option to specify for wich HTTP methods to create transactions on request)
antonpirker
changed the title
Don't trace OPTIONS and HEAD in [Flask] requests by default
Don't trace OPTIONS and HEAD in WSGI frameworks by default
Sep 13, 2024
Make sure that frameworks based on WSGI do not create transactions for the HTTP methods
OPTIONS
andHEAD
by default.For Django and Flask also add a config option to the integrations to specify which HTTP methods to create transactions for.
(For other smaller frameworks we keep the default of not creating
OPTIONS
andHEAD
transaction, but will add an option to specify for wich HTTP methods to create transactions on request)Docs PR:
getsentry/sentry-docs#11348
The text was updated successfully, but these errors were encountered: