The server supports a flexible and configurable access logging system that provides a full set of customized components to meet your system’s logging requirements.
The default access log can be configured to write information to a log file with two records per operation, one for the request received and one for the response returned. It can also be configured to write one message per operation or configured to record information about a subset of operations processed by the server. In addition to modifying existing default log files, you can create custom log publishers to monitor specific properties or connection criteria. For more information, see Creating New Log Publishers.
The server can be configured to use multiple access log publishers writing logs to different files using different configurations. This approach makes it possible to have fine-grained logging for various purposes, such as a log that contains only failed operations, a log that contains only operations requested by root users or a log that contains only operations that took longer than 20ms to complete.
The server provides an additional mechanism to filter access logs to record only a subset of messages of one or more types. The access log filtering mechanism uses the operation criteria (connection, request, result, search-entry, search-reference) to determine whether a given message should be logged based on information associated with the client connection as well as information in the operation request and response messages. For more information, see Configuring Filtered Logging.