Hi,
like 2-3 months ago or some. I test this at home on ltm vm image (and on nscaler vpx) but not on production, Rather then tomcats, It was glassfish app servers, similar to your setup.
""SNMP Dynamic Ratio""
Checking on system resources via snmp ++ i enable snmp proxy and gfs snmp and check other stuff too such as heap mem,threat counts,memory utilization, transcation manager, http listener threat connection counts and vice versa. Its effective and works well.On java side apps, i assume its better to monitor jvm then all system resources. Also easy to follow via cacti overall whats is going on for example. (my idea) . As long as nothing goes wrong with snmp traffic. Also as it shows on url you post, recommended healtcheck interval is too long 30 seconds on production for a fail node (snmp check criteria not met) is long time going to detect then going to relesect and dispatches it to other node not sure about that.
But the most impressive part is applying this method to mysql load balanced slaves, for example, Heavy queries came from crons vice versa, it stops traffic to them cause of snmp monitoring (perl has mysql-snmp monitoring as you know) and dispatches it to other nodes. The traffic comes from app servers i meant. Its hard to do tcp lb on sqls and monitor them but this method i tried works best for detecting sqls with lots of io usage.
These are my expriences from tests i did at home.
Take care friend. (İyi çalışmalar)