-
Notifications
You must be signed in to change notification settings - Fork 199
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
Application Insights showing 200 for failed requests #810
Comments
@DineshAyyapillai
|
@DineshAyyapillai, also please mention how you have instrumented your application. Are you using Springboot starter, or just plain SDK? |
@DineshAyyapillai thanks for mentioning that. @littleaj has a little more context on non springboot scenarios. Often it is possible that sometimes an error code is set in the request telemetry after the object escapes the filter chain. i.e by some error handler etc. In that case it is likely that request telemetry object might miss the result code. Also, it might be possible if you are using Async servlet request it might have issues similar to that. If possible . |
Essentially this is dup of #600 |
@dhaval24 Yeah, It's almost similar but any idea on whether the issue will be fixed in the upcoming releases of application insights or any alternative solutions to work on. |
we recommend manually tracking requests to handle async responses. We'll be providing guidance and code snippets to help with this in the next few weeks. at this point, we do not have an estimate on supporting it out of the box in ApplicationInsights SDK. |
moved the label to enhancements, as this is more about handling async requests. |
@DineshAyyapillai could you please also explain you entire scenario of how you are using async requests, so that we can capture the scenario correctly. |
Even from the latest application insights version 2.3.0, the Response code issue which is described in the below fix is not resolved,
#603
Did we find any better alternatives or solution for the issue?
With Regards,
Dinesh Ayyapillai.
The text was updated successfully, but these errors were encountered: