Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

HTTP 4xx errors are treated as errors #11635

Open
d33kayyy opened this issue Dec 8, 2024 · 0 comments
Open

HTTP 4xx errors are treated as errors #11635

d33kayyy opened this issue Dec 8, 2024 · 0 comments

Comments

@d33kayyy
Copy link

d33kayyy commented Dec 8, 2024

Hi, I recently upgraded my Python application from Python 3.10 to 3.12, hence I had to upgrade ddtrace from 1.20.19 to 2.16.1.

I noticed that now responses with HTTP 4xx are also considered as errors. I checked the documentation and found DD_TRACE_HTTP_SERVER_ERROR_STATUSES. However, I'm not setting it in my project that it should use the default, which must be status between 500-599.

Image

Libraries' versions

django==5.1.3
ddtrace==2.16.1
gunicorn==20.1.0
uvicorn==0.32.0

Running with

ddtrace-run gunicorn -w $HTTP_WORKER_COUNT -k example.asgi.UvicornWorker --bind 0.0.0.0:$PORT example.asgi:application
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant