mod_heartmonitor Centralized monitor for mod_heartbeat origin servers Experimental mod_heartmonitor.c heartmonitor_module Available in Apache 2.3 and later

mod_heartmonitor listens for server status messages generated by mod_heartbeat enabled origin servers and makes their status available to mod_lbmethod_heartbeat. This allows ProxyPass to use the "heartbeat" lbmethod inside of ProxyPass.

This module uses the services of mod_slotmem_shm when available instead of flat-file storage. No configuration is required to use mod_slotmem_shm.

To use mod_heartmonitor, mod_status and mod_watchdog must be either a static modules or, if a dynamic module, it must be loaded before mod_heartmonitor. HeartbeatListen multicast address to listen for incoming heartbeat requests HeartbeatListen addr:port disabled server config

The HeartbeatListen directive specifies the multicast address on which the server will listen for status information from mod_heartbeat-enabled servers. This address will usually correspond to a configured HeartbeatAddress on an origin server.

HeartbeatListen 239.0.0.1:27999

This module is inactive until this directive is used.

 HeartbeatStorage Path to store heartbeat data HeartbeatStorage file-path HeartbeatStorage logs/hb.dat server config

The HeartbeatStorage directive specifies the path to store heartbeat data. This flat-file is used only when mod_slotmem_shm is not loaded.

 HeartbeatMaxServers Specifies the maximum number of servers that will be sending heartbeat requests to this server HeartbeatMaxServers number-of-servers HeartbeatMaxServers 10 server config

The HeartbeatMaxServers directive specifies the maximum number of servers that will be sending requests to this monitor server. It is used to control the size of the shared memory allocated to store the heartbeat info when mod_slotmem_shm is in use.