For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

Dmitry_Kuzura's avatar
Dmitry_Kuzura
Icon for Nimbostratus rankNimbostratus
Mar 31, 2009

Custom alerts in 9.4.4 do not send email notifications

Greetings!   I'm banging my head against the wall..   custom alert from /conf/user_alert.conf does not send email notification when pool member is marked down by monitor.   /config/user...
management
monitoring
hwidjaja_37598's avatar
hwidjaja_37598
Icon for Altostratus rankAltostratus
Apr 03, 2009
It seems like the alertd uses /var/run/bigip_error_maps.dat file when it receives log message that matches an alert code (on this case, it's 01070638). The alertd process then performs the alert actions specified for that alert name in the /etc/alertd/alert.conf file.

 

 

Check this out: SOL6420 Click here

 

 

The setting would be:

 

 

alert BIGIP_MCPD_MCPDERR_POOL_MEMBER_MON_STATUS {

 

email toaddress="xxx@xxx.com"

 

fromaddress="root-bip1@xxx.com"

 

body="*** A pool member marked DOWN by monitor ***"

 

}

 

 

I found the Alert ID (BIGIP_MCPD_MCPDERR_POOL_MEMBER_MON_STATUS) from:

 

ltm grep 01070638 /var/run/bigip_error_maps.dat

 

0 LOG_NOTICE 01070638 BIGIP_MCPD_MCPDERR_POOL_MEMBER_MON_STATUS "Pool member %s:%u monitor status %s."

 

 

It could be changed from /etc/alertd/bigip_mcpd_error_maps.h file

 

 

I could not find a way to only send the email for a specific pool member. As an alternative, you can use syslog-ng to run log2mail when it sees this message. For more information, go to syslog-ng and log2mail manual:

 

 

man log2mail