Expand my Community achievements bar.

Don’t miss the AEM Skill Exchange in SF on Nov 14—hear from industry leaders, learn best practices, and enhance your AEM strategy with practical tips.
SOLVED

AEM OOB Health Reports / Monitoring - Do these report / monitoring cause AEM slowness

Avatar

Level 1

Hi,

AEM OOB provides Health Check Status and Monitoring Graphs. Does accessing these Health Check status or Monitoring Graphs cause any slowness to AEM.

 

Health Check 

http://localhost:4502/libs/granite/operations/content/healthreports/healthreportlist.html

 

Monitoring Graphs

http://localhost:4502/libs/granite/operations/content/monitoring/page.html

 

Questions:

1) These Health Check or Monitoring Graph (which reports on Memory / Disk Usage / Query cache / Indexes etc) reports in real time - So wondering if this causes extra load on AEM server repeatedly to gather data.

 

2) Also if it OK to run such reports at regular interval like every 4 hour on AEM Publisher in Production ?

 

Thanks in advance.

 

1 Accepted Solution

Avatar

Correct answer by
Level 10

Hi @rohit-pathak-2020,

  1. If you are worried that your customers will experience a performance drop if you check the reports, the answer is... yes but no...  Technically you are correct, the reports are updated in real-time so there will be an impact on the instance's performance, however:
    1. The impact is negligible unless you have a HUGE amount of content
    2. If you are using a Dispatcher (as you absolutely should!) then the customer will see no difference sine the content is largely being served from cache.

  2. I'm not sure what you mean by "OK" but for the reasons I mentioned above, there should be little to no impact for running these reports 

View solution in original post

2 Replies

Avatar

Correct answer by
Level 10

Hi @rohit-pathak-2020,

  1. If you are worried that your customers will experience a performance drop if you check the reports, the answer is... yes but no...  Technically you are correct, the reports are updated in real-time so there will be an impact on the instance's performance, however:
    1. The impact is negligible unless you have a HUGE amount of content
    2. If you are using a Dispatcher (as you absolutely should!) then the customer will see no difference sine the content is largely being served from cache.

  2. I'm not sure what you mean by "OK" but for the reasons I mentioned above, there should be little to no impact for running these reports