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
We have upgraded the Application Insights to V 2.22.0 and thend deployed the application to live azure service app on the 15th May 2024. After the upgrade we have noticed that there are no more result code 0 / status code 0 exceptions logged on Application Insights. We can see few of 499 requests but not 0 anymore. If we search for the dates older than 15th May 2024 we can see the resultCode 0.
Kindly advise where the things are gone wrong and what needs to be done to find out resultCode 0. Also I have read that 499 code is now used widely on azure to record the undefined / user cancelled action exceptions etc but is it something that 0 is now been replaced with 499.
I have to report to my SMT every week therefore I need a proper answer for them for any kind of change please.
The text was updated successfully, but these errors were encountered:
We have upgraded the Application Insights to V 2.22.0 and thend deployed the application to live azure service app on the 15th May 2024. After the upgrade we have noticed that there are no more result code 0 / status code 0 exceptions logged on Application Insights. We can see few of 499 requests but not 0 anymore. If we search for the dates older than 15th May 2024 we can see the resultCode 0.
Kindly advise where the things are gone wrong and what needs to be done to find out resultCode 0. Also I have read that 499 code is now used widely on azure to record the undefined / user cancelled action exceptions etc but is it something that 0 is now been replaced with 499.
I have to report to my SMT every week therefore I need a proper answer for them for any kind of change please.
The text was updated successfully, but these errors were encountered: