I can't seem to allow zabbix to monitor two agents on the same IP address with auto-discovery -- their "Add host" actions conflict each other.
I have a standard zabbix agent on port 10050, and a zapcat java agent on port 10052.
An auto-discovery rule is created for each, for zabbix agent on port 10050 and another on 10052.
I've tried to chose the key "jmx[java.lang:type=Runtime][Name]" for the device uniqueness criteria for the zapcat discovery configuration because it includes the PID of the JVM with the hostname, instead of the hostname from "jmx[jboss.system:type=ServerInfo][HostName]", but that doesn't seem to help distinguish the two different discoveries at the "Add host" action.
Furthermore, for the Discovery Actions, i distinguish "Discovery Solaris Zones" rule from the "Discover Zapcat monitored JVMs" rule by their Service Port that must be either 10050 or 10052. I chose "Add host" as an action for both, but link them to different templates.
After some time, I end up with a single host record that includes all of the templates combined, with the zabbix agent configured for port 10050 only. Then i begin receiving alerts about not being able to retrieve critical jmx attributes.
Any suggestions? How do I monitor both the host AND a zapcat jvm on the same machine through auto-discovery? Should I resort to manually adding the zapcat monitored machines only? (Only 50-100 compared to thousands of the other kind)
I have a standard zabbix agent on port 10050, and a zapcat java agent on port 10052.
An auto-discovery rule is created for each, for zabbix agent on port 10050 and another on 10052.
I've tried to chose the key "jmx[java.lang:type=Runtime][Name]" for the device uniqueness criteria for the zapcat discovery configuration because it includes the PID of the JVM with the hostname, instead of the hostname from "jmx[jboss.system:type=ServerInfo][HostName]", but that doesn't seem to help distinguish the two different discoveries at the "Add host" action.
Furthermore, for the Discovery Actions, i distinguish "Discovery Solaris Zones" rule from the "Discover Zapcat monitored JVMs" rule by their Service Port that must be either 10050 or 10052. I chose "Add host" as an action for both, but link them to different templates.
After some time, I end up with a single host record that includes all of the templates combined, with the zabbix agent configured for port 10050 only. Then i begin receiving alerts about not being able to retrieve critical jmx attributes.
Any suggestions? How do I monitor both the host AND a zapcat jvm on the same machine through auto-discovery? Should I resort to manually adding the zapcat monitored machines only? (Only 50-100 compared to thousands of the other kind)
Comment