Forum Discussion

fabianlumy's avatar
fabianlumy
Icon for Nimbostratus rankNimbostratus
Feb 19, 2013

HTTP health monitor detail on error

Hello everybody,

 

 

Is anyone know if there is a way to get some defails about failed http health monitor ? (For example: http response code, body content, etc...)

 

The only way I've found to achieve this is to enable "bigd.debug" , but it's not a solution for a production environnement.

 

For monitor health which include few monitor check, without debug, I don't know how to identify the faulty check...

 

 

Thanks for your idea about this...

 

5 Replies

  • I tend to use CURL to mimick the monitors as close as possible. Another way to see what's going on is to do a TCPDump on the non-floating self IP on the node's VLAN. Specify the node's IP, the self IP and the internal vlan. You might also consider doing a TCPDump from the node / pool member and filter on the non-floating self ip.

     

     

    John
  • You can do two things. No. 2 will give you the most detail;

     

     

    1) Use the tmsh run util test-monitor command (v10 onwards only)

     

    2) Use tcpdump to capture the monitor traffic, for instance: tcpdump -i 'vlan_name' -vv -nn -X -s0 src host 'f5-ip' and dst host 'real-server-ip (obviously be vary care in a production environment)
  • Thanks for your suggestions, the problem is to find a solution for anytime, not for a oneshot.

     

    Obvisouly I cannot run a permanent tcpdump :)

     

    What I'm looking for, is a solution which "log" information about http session which cause a faulty check.

     

     

    When a node has been down for 1 minutes, I would like to be able a know what the node has respond to the health check...
  • I think an external monitor is perhaps your best bet. Using the cURL syntax that John spoke of above, you can fashion an external HTTP to do as much or more than the built-in GUI monitor, plus have the ability to consume as much response data as you want from the failed servers for logging.
  • Yes, I think I will try with external monitor using curl, and add some log informations.

     

    Thanks for you help