How to check the cpu utilization for particular Environment in aem as cloud service?

[sai_charanAr]

Hi all,
Is there a way to check CPU utilization in AEM as a Cloud Service? I couldn’t find any direct option in Cloud Manager or logs. Any tips or best practices for monitoring performance would be helpful.

Thanks!

[giuseppebag · Accepted solution]

Customers do not have access to raw CPU utilisation statistics (such as per-core usage or system load averages) through Cloud Manager or the AEM UI. Adobe continuously monitors infrastructure health, including CPU iowait and other thresholds, using hundreds of internal monitors. If thresholds are breached, Adobe’s operations team is alerted and may take proactive action: https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/operations/monit... 

Customers can use the built-in New Relic Application Performance Monitoring (APM) suite to observe JVM-level metrics, transaction timing, and application performance, but not direct OS-level CPU statistics: https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/usi... 

[deepak_singla]

Hi @sai_charanAr 

I’ve run into this question myself while working with AEM as a Cloud Service. Unfortunately, there isn’t a way to directly view CPU utilization like we could in on-prem or AMS setups. That said, there are a few things I’ve found helpful for monitoring performance:

1. Cloud Manager Monitoring

Cloud Manager doesn’t expose CPU stats directly, but it does provide some helpful KPIs during pipeline performance testing — like response times, throughput, and error rates. While not a substitute for CPU metrics, they can help flag performance issues early.

2. New Relic (Internal Monitoring)

Adobe uses New Relic for internal monitoring, and while it's not directly available to customers, in the past I’ve reached out via Adobe Support and they've been able to share specific metrics (CPU, memory, etc.) when troubleshooting.

3. Logs & Developer Console

You can also use the AEM Dev Console and logs in Cloud Manager to watch for symptoms of resource stress — things like slow requests, timeouts, long-running queries, or heavy workflows. These usually correlate with backend resource usage.