We recommend to use VisualVM to monitor an Axon.ivy Engine. VisualVM allows to monitor the memory and CPU usage of an Axon.ivy Engine process. It can also be used to analyze problems in your Axon.ivy projects, like memory leaks or thread dead locks.
VisualVM can connect to all Java processes running on the same host and with the same user. In addition, you can use JMX (See section Java Management Extension for more information) to connect VisualVM to processes that run under another user (e.g. as Windows Service) or on remote machines.
VisualVM is available for download on GitHub: https://visualvm.github.io/.
Axon.ivy VisualVM Plugin¶
In the Axon.ivy Market we provide a dedicated plugin for VisualVM that allows to monitor some of the technical aspects of an Axon.ivy Engine. For example, you can observe the current transactions on the System Database, whether you violate the licence or how many requests are running on an Axon.ivy Engine at any given time. And in the same tool you can still observe the heap or CPU usage or create thread dumps.
VisualVM is a tool to observe the current state of a monitored engine. It is not intended for long-time monitoring, recording or to trigger alarm events. If you want to do that, use the Axon.ivy JMX extensions in combination with tools like Nagios or IBM Tivoli.
The plugin is consisting of multiple tabs for different aspects. Most of the tabs contain charts structured similar to this: