Describe the bug
No trace is sent to Dynatrace on detected bad requests (HTTP status 400), when using the stack starlette:0.32.0.post1 + connexion:3.0.5 + flask:3.0.0.
When doing some other tests, I see tracing of requests for there use cases:
200: successful request handled
404: no resource found
500: internal error
Here is my observation. The new version of connexion (v3 - ASGI) handles the request before delegating to flask. In the different scenarios listed above, successful processing, no resource found or internal error, they all pass through flask code. The case of bd request, connexion detects the base request and calls its error handling mechanism (which can be overriden)
To Reproduce
Steps to reproduce the behavior:
Create a dummy application using the connexion guideline, using FlaskApp, with simple openapi definition, adding a dependency on autodynatrace and appropriate configuration
Send an valid vs invalid request
Dynatrace will contain only the successful traces
No error found in log...
Expected behavior
I would expect that the bad requests be reported in Dynatrace.
Describe the bug No trace is sent to Dynatrace on detected bad requests (HTTP status 400), when using the stack starlette:0.32.0.post1 + connexion:3.0.5 + flask:3.0.0.
When doing some other tests, I see tracing of requests for there use cases:
Here is my observation. The new version of connexion (v3 - ASGI) handles the request before delegating to flask. In the different scenarios listed above, successful processing, no resource found or internal error, they all pass through flask code. The case of bd request, connexion detects the base request and calls its error handling mechanism (which can be overriden)
To Reproduce Steps to reproduce the behavior:
Expected behavior I would expect that the bad requests be reported in Dynatrace.
Thanks in advance for your help.