This repository was archived by the owner on Feb 28, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 14
Home
Puneet Gupta edited this page Nov 24, 2020
·
6 revisions
DaaS (Diagnostics As A Service) is a pre-installed site extension installed on Azure App Service Windows instances. It is installed in %ProgramFiles(x86)%\SiteExtensions\DAAS
folder on the instances serving your web apps and it provides API's that are used by the Diagnose and Solve portal to run different Diagnostic tools like CLR Profiler, CPU Monitoring, Memory Dumps, Java Flight Recorder, etc.
There are two parts to DaaS :-
- The DaaS Site Extension - The DAAS Site extension serves requests to all the DAAS API invoked via Diagnose and Solve Portal.
- DaaSRunner Web Job - The DaasRunner webjob helps in collecting data on each instance where your app is running. On the first request to the DaaS site extension, this webjob is created.
For DaaS to work smoothly, all the below requirements must be met. The Diagnose and Solve Portal
- The Site should be running on a Dedicated SKU
- Since DaasRunner is a continuous web job, the Always On option for the app should be enabled
- Local Cache should be turned OFF. With local cache enabled, you cannot invoke the Diagnostic Tools via Autohealing and you will see inconsistent experience when using the diagnostic tools even manually. The current workaround is to either disable Local Cache or switch to Run your app from a Zip Package.
You can check the latest version by going to D:\Program Files (x86)\SiteExtensions\DaaS
folder from the KUDU console for the web app.