cfaf2af197 | ||
---|---|---|
data | ||
infrastructure | ||
src | ||
tests | ||
.gitignore | ||
.travis.yml | ||
Diagnostics.sln | ||
LICENSE | ||
README.md | ||
antares.external.diagnostics.compilerhost.nuspec | ||
antares.external.diagnostics.runtimehost.nuspec | ||
azure-nationalcloud-pipelines.yml | ||
azure-pipelines.yml | ||
build.cmd | ||
ca.ruleset | ||
nuget.config | ||
origin) |
README.md
⛔️ DEPRECATED
This project has been migrated over into an internal repository. While we may not be tracking or accepting new issues here in this repo, please feel free to use our feedback channel in our Diagnose and Solve blade in Azure Portal
Azure App Service Diagnostics
When you’re running a web application, you want to be prepared for any issues that may arise, from 500 errors to your users telling you that your site is down. App Service diagnostics is an intelligent and interactive experience to help you troubleshoot your app with no configuration required. When you do run into issues with your app, App Service diagnostics points out what’s wrong to guide you to the right information to more easily and quickly troubleshoot and resolve the issue.
What is supported?
App Service Diagnostics can diagnose issues on these types of resources:
Getting Started
- Open App Service Diagnostics
- Using the interactive interface
- Understanding the diagnostic reports
- Health checkup Graphs
- Diagnotics tools for Windows Web app
- Change analysis: Correlate code changes to application issues
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.