January 2, 2021
Estimated Post Reading Time ~

AEM-Zabbix Monitoring Demo

This AEM-Zabbix Monitoring Demo package contains a configured and running Zabbix that will connect to a local instance of your running AEM Author. Once running, you can look around Zabbix and observe the dashboard as it monitors your AEM instance. 

From the dashboard, you can a live scrape of your Author instance, useable disk space, memory allocation, and a few more monitored items. You can also trigger events and notifications and watch how the dashboard will alert you of any issues and problems.



Please make sure you have the following files installed:
  • digitalctrl_aem_monitoring.tar
  • zabbix.tar.bz2
Source:
https://drive.google.com/drive/folders/1gD3VO9lw-EgjJ8qebd5dbEcQzdIH7a6-

Requirements
You would need the following applications installed on your local environment:
  • AEM Author (version 6.x)
  • Docker (version 2.2.x)
  • Internet Browser (Chrome, Firefox or others)
You would also need at least 50 MB of disk space and 8GB of RAM.

AEM
For this monitoring package to work, we need a default local installation of AEM Author listening to port 4502. We also need to start AEM to listen to port 9091 for the JMX agent.
  • Add the following as part of the start-up for your AEM instance:-Dcom.sun.management.jmxremote.port=9091 \ -Dcom.sun.management.jmxremote.rmi.port=9091 \ -Dcom.sun.management.jmxremote.ssl=false \ -Dcom.sun.management.jmxremote.authenticate=false \ -Dcom.sun.management.jmxremote \ -Djava.rmi.server.hostname=host.docker.internal
These added start-up parameters will need to be added to your start script (/crx-quickstart/bin/start). It would be similar to the image below:


Docker
Docker is a tool designed to make it easier to create, deploy, and run applications by using containers. Containers allow a developer to package up an application with all of the parts it needs, such as libraries and other dependencies, and deploy it as one package.

Download the Docker Zabbix image and volume mount (as mentioned above)
  • digitalctrl_aem_monitoring.tar
  • zabbix.tar.bz2
Download the backup utility for Docker 
# docker pull loomchild/volume-backup

Load the image
# docker load -i digitalctrl_aem_monitoring.tar

Check to make sure the image is loaded
# docker images

Unpack and mount the volume backup
# docker run -v zbx_env:/volume -v /location_of_volume_backup/backup --rm loomchild/volume-backup restore zabbix.tar.bz2

Run the Docker Zabbix image
# docker run -p 80:80 -p 10051:10051 -d -v zbx_env:/var/lib/mysql digitalctrl_aem_monitoring

Check Zabbix (wait until Docker is done loading the image)
You should have a similar screen loaded for the dashboard:


* Make sure your local AEM Author instance is running on port 4502 with port 9091 open (as described in the instruction above)

Zabbix is currently monitoring the following:
  • Disk Space
  • Segment Store Size
  • Memory Usage
  • Session Count
  • Replication Queue
  • AEM Instance
Questions
If you have any questions on this monitoring demo package or require further consultation on a holistic approach to monitoring your organization’s AEM ecosystem both from a strategic and/or a technical perspective, please don’t hesitate to reach out.

Reference
If you need a quick guide on how Zabbix is used to monitor AEM, please refer to my other blog at the following location:
https://www.howtoaem.com/post/aem-monitoring-via-zabbix


By aem4beginner

No comments:

Post a Comment

If you have any doubts or questions, please let us know.