question

AhmadMustafa-3218 avatar image
0 Votes"
AhmadMustafa-3218 asked ajkuma-MSFT commented

My Metrics Azure Monitoring show error http 5xx from some time and logs shows cup usage but monitor shows it was normal

My azure monitor shows http 5xx error. It happens before but stable then it happen again from some days When I see diagnostic Detail logs it shows


 Heartbeat took longer than "00:00:01" at "09/04/2021 01:08:21 +00:00"

But when I show server CPU monitor log it shows normal usage you can see 30 days usage below

129289-image.png

Here is Http error from azure monitor screen shot
129332-image.png

Here is diagnostics reports shows why errors came
129247-image.png

What I have tried is :
Restarted Server
Upscale instance Vertically/Horizontally

I am so confused what should I do ?


azure-webapps
image.png (45.2 KiB)
image.png (11.5 KiB)
image.png (34.3 KiB)
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

1 Answer

ajkuma-MSFT avatar image
0 Votes"
ajkuma-MSFT answered ajkuma-MSFT commented

@AhmadMustafa-3218, Firstly, apologies for the delayed response on this from over the weekend.

On which region have you provisioned your WebApp? App Service - Central US or Application Insights - West Europe? What’s the exact time in UTC that you experienced these issues?

You may review your Azure Service Health alerts, there were a couple of issues identified which were mitigated.

From Azure Portal alert:
Summary of Impact:
Between 15:44 UTC and 18:09 UTC on 03 Sep 2021, you have been identified as a customer using Apps Service in Central US who may have received intermittent HTTP 500-level response codes or timeouts when accessing their resources via HTTP or HTTPS.

Preliminary Root Cause:
An increase in the number of incoming requests to a single underlying endpoint led to that endpoint reaching an operational threshold, causing some connections to fail.
Mitigation: We manually throttled incoming traffic.

Next Steps: We will continue to investigate to establish the full root cause and identify necessary repairs and preventative actions to help deter issues like this from occurring.

· 3
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Also,

From Azure Portal:
Summary of Impact:
Between 08:53 UTC and 10:05 UTC on 06 Sep 2021, you were identified as a customer using Application Insights in West Europe who may have experienced issues accessing your data as well as missed or delayed alerts.

Preliminary Root Cause: We determined that an instance of a backend service responsible for processing requests became unhealthy after reaching an operational threshold.

Mitigation: This issue was self-healed by the Azure platform once our system auto-scaled.

Next steps: We will continue to investigate to establish the full root cause and prevent future occurrences.

-Stay informed about Azure service issues by creating custom service health alerts: https://aka.ms/ash-videos for video tutorials and https://aka.ms/ash-alerts for how-to documentation.

Apologies for all the inconvenience with this issue. Please let us know if the issue still persists, I’ll follow-up with you further for an immediate solution.

0 Votes 0 ·

Yes the issue is still persist it happen again on 7 of september .

0 Votes 0 ·
ajkuma-MSFT avatar image ajkuma-MSFT AhmadMustafa-3218 ·

Apologies you're still experiencing this issue. I have followed-up with you privately for a deeper investigation.

0 Votes 0 ·