Forum Discussion
Kai_Wilke
Feb 29, 2016MVP
Hi Piotr,
personally I'm using a dynamic pool status page on every HTTP-enabled Virtual Server for health minitoring.
The page will enumerate the currently selected pool and display the online/offline status of each pool member (this page can be used for PingDOM to monitor the health of each server). But the page has also two additional gimmics to access a specific node by using a.) a query string of
?f5action=select&node=[NodeID]
(e.g for PingDom Monitoring) or by injecting a HTTP-cookie (via HTML buttons) to tie a specific browser session to a specific node (e.g. useful for developers to troubleshoot a single node).
Compared to your outlined logic my status page approach wouldn't add additional overhead to monitor each pool and also monitor and access each single pool members. The status page information is dynamically generated based on just the currently selected pool.
Note: Did send you an PM to show you my monitoring page in action... 😉
Cheers, Kai