An Azure app service shares CPU time with the rest of the app services in its app service plan. Therefore, it’s important to keep an eye out for CPU use that could affect all app services in the same plan. Blue Matador automatically watches the CPUTime metric for anomalous behavior.


    By itself, higher CPU time is probably not a cause for concern. However, when correlated with other issues in your app service, you may see degraded application performance for all app services sharing the app service plan.



    The root causes for high CPU time are likely related to your application, but the troubleshooting steps are the same for most applications:

    1. If you see performance degradation in the affected app service or any other app service using the app service plan, temporarily scale out (or scale up if you are at the limits of your pricing tier) while you fix the issue.
    2. Enable and check the diagnostic logs for your app service. Fix any application issues you may find in the logs.