Skip to content
A Zabbix template for pacemaker cluster monitoring with virtual ip
Branch: master
Clone or download
Latest commit 4d4af8c Jul 6, 2018
Type Name Latest commit message Commit time
Failed to load latest commit information.
configs Initial commit Oct 20, 2017
LICENSE Merge branch 'master' of Oct 23, 2017
template_app_pacemaker.xml triggers fixed Oct 23, 2017

Zabbix Pacemaker Template

A Zabbix template for pacemaker cluster monitoring with virtual ip.

Author: Vadim Ipatov <> (



Metric Description
pacemaker.cluster.dc Current cluster DC (Designated Coordinator)
pacemaker.cluster.failed_actions The current number of failed actions
pacemaker.cluster.maintenance Shows if the cluster is in the maintenance state
pacemaker.nodes.offline The current number of offline (or in the shutdown state) nodes Shows if corosync daemon is in the running state Shows if pacemakerd daemon is in the running state
pacemaker.resources.failed The current number of failed (non active or blocked) resources
pacemaker.status Service item for data gathering
system.hostname Node hostname. If it changes, it could mean that the VIP has been moved to another node


You need to configure every cluster nodes as shown below:

  • Copy "configs/pacemaker.conf" into your zabbix_agent include folder (default: /etc/zabbix/zabbix_agentd.d/) or manually add that UserParameter to config:

UserParameter=pacemaker.status, sudo /usr/sbin/crm_mon --as-xml

  • Restart zabbix_agent

  • Copy "configs/zbx_pacemaker.sudoers" into /etc/sudoers.d or manually add that rule:

zabbix ALL=NOPASSWD: /usr/sbin/crm_mon --as-xml

  • Import "template_app_pacemaker.xml" into zabbix as template
  • Create "virtual" host object with virtual ip address as network interface and link this template.


You can check that everything works correctly by using crm_mon dumps in “tests” folder.

For this purpose you need to copy dumps to cluster nodes (or use your own) and add this UserParameter to config:

UserParameter=pacemaker.test[*], cat /etc/zabbix/zabbix_agentd.d/tests/$1

Then change "pacemaker.status" item key to "pacemaker.test[sampleN.xml]" and save.

Also you could manually edit sample file for test different cluster states.

You can’t perform that action at this time.