Hello, I'm trying to put together a good monitoring strategy to keep Artemis healthy. I set up Zabbix, which is working pretty well, and I'm using jconsole to explore the JMX MBeans and troubleshoot.
Right now I only have two alerts. One that watech for the secondary cluster to come up, and sends an email alert that the primary has failed. And a second where I divide HeapMemoryUsage.used by HeapMemoryUsage.max and send an alert if it's greater than 0.7. It's been suggested that I should monitor garbage collections -- the amount of CPU time spent and number of collections -- to detect if I'm running out of memory. I've also tried out this Zabbix template: https://github.com/topicusoverheid/zabbix-activmq-template It doesn't seem to work in Artemis though. After importing it, two "applications" are created (in Zabbix terms) but no "items" are created. I've tried out some of the MBeans it uses though. I don't think this is what I need though. Is there any guidance on this? A best practices or example showing all the different MBeans and how they're used to detect the kinds of problems Artemis is likely to run into? Thanks, Ben
