Monitor Logs do not show which pool it is referring to

Another thought, although not an iRules solution:

You can create a custom monitor (based on the shell script on the LTM filesystem @ /usr/bin/monitors/sample_monitor) which takes the pool name as an input variable and outputs a more descriptive log message upon node failure.

If you are careful that your log message still matches the expression in /etc/alertd/alert.conf

("Pool member (.*?) : (.*?) monitor status down.")
(except without the spaces around the colon)

you will still receive traps when a pool member goes down.

HTH

/deb