Hi, On Wed, Aug 26, 2009 at 02:00:42PM -0700, Jonah Horowitz wrote: > I???m watching my servers on the back end and occasionally they flap. I???m > wondering if there is a way to see why they are taken out of service. I???d > like to see the actual response, or at least a HTTP status code.
right now it's not archived. I would like to keep a local copy of the last request sent and response received which caused a state change, but that's not implemented yet. I wanted to clean up the stats socket first, but now I realize that we could keep at least some info (eg: HTTP status, timeout, ...) in the server struct itself and report it in the log. Nothing of that is performed right now, so you may have to tcpdump at best :-( One trick you can do to make this experience better is to set a "port" or "addr" option on your server line to run the checks on a different ip/port combination. That way, you can filter that on tcpdump and only get the checks. Willy
