Highlighted

Monitoring AEM via JConsole | AEM Community Blog Seeding

Avatar

Avatar

kautuk_sahni

Community Manager

Total Posts

(val/1000)?string[".0"]}K

Likes

955

Correct Answer

(val/1000)?string[".0"]}K

Avatar

kautuk_sahni

Community Manager

Total Posts

(val/1000)?string[".0"]}K

Likes

955

Correct Answer

(val/1000)?string[".0"]}K
kautuk_sahni
Community Manager

21-05-2020

BlogImage.jpg

Monitoring AEM via JConsole by howtoaem Blog

Abstract

Sometimes, the Out of the Box (OOTB) monitoring that comes with AEM is not enough and we need a better way to monitor our AEM instances. AEM allows external monitoring applications to interact with Managed Beans (MBeans) via Java Management Extensions (JMX). Using applications such as JConsole or other enterprise-level monitoring applications, users can monitor these MBeans objects as well as performance and resource usages of AEM.

Some of the registered MBeans that can be monitored via JMX:
1.Repository
2.Replication Agents
3.Sling Engine
4.Metrics
5.Workflows

System resources such as memory, threads and classes can also be monitored via these monitoring applications.
The ideal solution is to have an enterprise level monitoring in placed but the next best thing is to use a local tool such as JConsole to give us some insights on what a proper monitoring strategy can look like. This is a simple instruction of getting using JConsole to quickly monitor AEM and for this proof of concept (POC), we are going to use a local running AEM Author instance.

Read Full Blog

Monitoring AEM via JConsole

Q&A

Please use this thread to ask the related questions.

AEM AEMEBlogSeeding Experience Manager