Thanks Ed.
I went to implementing a custom Perl script to parse details from the ltm log entry that triggers the SNMP alert. Issue I'm having now is that a "No members available for pool" alert is also triggering my "Node status Down" alert which is resulting in the alert being processed twice in 2 different fashions.
Here is the error in the ltm log:
Feb 5 09:09:08 tmm err tmm[5905]: 01010028:3: No members available for pool /Common/test_pool
Here are the 2 custom alerts that seem both to be triggered:
alert CUSTOM_GENERAL_POOL_NO_MEMBER "No members available for pool (.*?)" {
exec command="/root/customAlertHandler.pl general"
}
alert CUSTOM_ERROR_POOL_MEMBER_STATUS_NODEDOWN "Pool (.*?) member (.*?) monitor status node down\." {
exec command="/root/customAlertHandler.pl nodeDown"
}
I'm unable to figure out why the Node Down alert is also being triggered by that error. Any ideas?