Logging HTTP transactions has associated costs. Access Gateway is capable of handling thousands of transactions per second. If the transaction volume is high and each log entry consumes a few hundred bytes, Access Gateway can fill up the available disk space in a matter of minutes. HTTP logging also increases system overhead, which causes some degradation in performance. By default, the logging of HTTP transactions is turned off. Before enabling logging, you need to determine what needs to be logged and then plan a logging strategy. For information about custom log formats, see Apache Log Configuration Module.