Logging Monitor Probe failures?

I don't know of a way to do this. By default, I don't think anything is logged when an individual monitor request fails. It's only when no valid response is received over the period of the timeout that the member is marked down and a log entry is generated.

 

 

If you wanted to check for client traffic failing, you could add a rule which logs a custom entry from LB_FAILED and configure a custom syslog alert based on the log string. Not sure if this is helps you though.

 

 

Aaron

Is there a way to log "which" monitor failed when one of multiple monitors on a pool member fails? I have nodes in a pool which have two health monitors and in the pool an Availability Requirement of "ALL" monitors, however all I see in the LTM log is "Pool member 1.2.3.4:80 monitor status down." I cannot tell which of the two monitors failed, assumuing it's only one of them, to know which app specific monitor I should be diagnosing.

Sure. You can enable a database key to instruct bigd to print the monitor name which failed when a pool member is marked down by running 'b db bigd.lognodestatuschange enable' from the command line. See this post for details:

 

 

Email notification of node/vs down

 

http://devcentral.f5.com/Default.aspx?tabid=53&forumid=31&tpage=2&view=topic&postid=2016728526

 

 

Also, you can enable debug on the monitoring daemon, bigd, by running 'b db bigd.debug enable' at the command line. The output is written to /var/log/bigdlog. The logging is very verbose so disable the logging once you're done collecting logs (using 'b db bigd.debug disable').

 

 

Aaron

You can enable bigd debugging, enter at the cli:

 

 

b db bigd.debug enable

 

 

Messages are in /var/log/bigdlog.

Thanks folks. I've turned on the lognodestatuschange and it's giving me exactly what I need. I already have a few bites on it!