AEM:6.3 we are trying to monitor jvm metrics(heap space) of AEM using Elastic search (ELK) | Community
Skip to main content
Gopalam
January 22, 2021
Solved

AEM:6.3 we are trying to monitor jvm metrics(heap space) of AEM using Elastic search (ELK)

  • January 22, 2021
  • 1 reply
  • 1356 views

Hi All

we are currently facing heap space issue on AEM.

The leak was found and it was fixed with help of AEM documentation.

1. Increasing heap memory

2. https://www.oracle.com/java/technologies/javase/vmoptions-jsp.html#DebuggingOptions

3. Use the flag "-XX:-UseGCOverheadLimit" to over come the error. we will disable the error occurrence.

4. change the instance type( we are using AWS)

5. use minimum 16 GB RAM.

 

The leakage was controlled by using above solution.

 

Our usecase is , we would like to monitor and create watcher and alerts using ELK.

we came across the ELK- metric beats ( there is a module- jolokia, this agent is used to get the jvm metrics)

 

here is the question:

Did anyone come across this setup?

 

Please let me know if some configured jolokia agent on AEM.

 

Thanks in advance

 

@joerghoh 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Kunal_Gaba_

You can connect it to running AEM instance JVM to monitor the stats of standard JVM provided and AEM specific Mbeans. 

In your AEM startup script you need to add the following system variable. 

-Dcom.sun.management.jmxremote.port=portNum

If you require authentication then you can set it via -

  -Dcom.sun.management.jmxremote.password.file=pwFilePath
  -Dcom.sun.management.jmxremote.port=8463
 

More details can be found here-

https://helpx.adobe.com/in/experience-manager/6-3/sites/administering/using/jmx-console.html#UsingExternalJMXApplicationsforMonitoring 

https://github.com/bkkhoo/jolokia-demo 

1 reply

Kunal_Gaba_
Kunal_Gaba_Accepted solution
January 22, 2021

You can connect it to running AEM instance JVM to monitor the stats of standard JVM provided and AEM specific Mbeans. 

In your AEM startup script you need to add the following system variable. 

-Dcom.sun.management.jmxremote.port=portNum

If you require authentication then you can set it via -

  -Dcom.sun.management.jmxremote.password.file=pwFilePath
  -Dcom.sun.management.jmxremote.port=8463
 

More details can be found here-

https://helpx.adobe.com/in/experience-manager/6-3/sites/administering/using/jmx-console.html#UsingExternalJMXApplicationsforMonitoring 

https://github.com/bkkhoo/jolokia-demo