access_log equivalent for a virtual server

Thanks for the response. Both work for me. Since I'm already using a syslog that dumps to disk, both are the same to me, too.

 

 

The advantage to direct disk support would be the common log formats out there and the harvesting tools built up around those formats.

 

 

I'd imagine that if you made this part of the core traffic engine, the logging operations would not be synchronous so mostly the issue would be how much memory you could spare to buffer the logging statements until they could be sent to disk or to a networked syslog.

 

 

If you made the option at the VS level, I'd ask for the ability to hold off new connections until the log is flushed or slow the connections down so the client can't send new requests as quickly. Things would be fine in a bursty scenario because the buffer might fill but would quickly fall. Sustained throughput would be problem, though. In my use cases, I require absolute logging, even at the expense of not accepting new connections as quickly. Other sites might like to get content traffic through at the expense of logging.