Azure App Service Crash Monitoring "stuck"

Hey Daniel, Sorry to hear that

Please follow this instruction at the end of the best thing to do is to contact azure support team opening a ticket on the Azure Portal because sound like something is wrong on the backend.

1. Verify Storage Account Accessibility

Crash Monitoring in Azure App Service relies on a Storage Account to store diagnostic data. If the Web App cannot access this Storage Account, it may cause the monitoring page to hang. To ensure proper connectivity:

Validate SAS URI: Use the following URL to check if your Web App can access the Storage Account (replace YOURAPPNAME with your app's name):

arduino

Copy

Edit

https://YOURAPPNAME.scm.azurewebsites.net/daas/api/settings/validatesasuri

If the validation fails, there may be network restrictions or misconfigurations preventing access.

Network Configurations: If your Web App is integrated with a Virtual Network (VNet), ensure that the Storage Account is accessible from within the VNet. Network restrictions can impede the Crash Monitoring feature. Consider temporarily relaxing these restrictions to see if it resolves the issue.

2. Check for Conflicting Extensions

Third-party extensions, such as monitoring agents, can sometimes interfere with Azure's built-in diagnostic tools. If you have extensions like Dynatrace OneAgent installed:

Temporarily Disable or Remove Extensions: Try disabling or uninstalling these extensions to determine if they are causing the conflict. For instance, removing Dynatrace OneAgent has been reported to resolve similar issues.

KIRANPATILS.COM

3. Inspect Kudu Console Processes

The Kudu console provides insights into the processes running within your Web App:

Access Kudu Console: Navigate to https://YOURAPPNAME.scm.azurewebsites.net/DebugConsole.

Check for Diagnostic Processes: Look for processes like CrashMon.exe, procdump.exe, or dbghost.exe. The presence of these processes indicates that Crash Monitoring is actively running. If they are absent, it suggests that the monitoring setup is incomplete or malfunctioning.

KIRANPATILS.COM

4. Reconfigure Crash Monitoring

If the issue persists, consider resetting the Crash Monitoring configuration:

Disable Crash Monitoring: Add the app setting WEBSITE_PROACTIVE_CRASHMONITORING_ENABLED and set it to FALSE. This action disables the proactive crash monitoring feature.

Restart the Web App: After applying the change, restart your Web App to ensure the setting takes effect.

Re-enable Crash Monitoring: Remove the WEBSITE_PROACTIVE_CRASHMONITORING_ENABLED setting or set it to TRUE to re-enable the feature.

This process can help reset the monitoring feature and potentially resolve the loading issue.

5. Contact Azure Support

If none of the above steps resolve the issue, it would be prudent to reach out to Azure Support. They can provide deeper insights and assist with backend diagnostics to identify and fix the problem.