Access |
Provides the requests received and responses
returned by the Directory Server. The information can be used to
understand the operations performed by clients and to debug problems with the
client applications. It can also be used for collecting usage information for
performance and capacity planning purposes. There are tools described later that
can analyze the access log to provide summaries of the LDAP activity and
performance. |
|
File-based Audit Log |
Special type of access logger that provides detailed information
about changes processed within the server. Disabled by default.
- Data Recovery Log. Publishes information about each write
operation processed in the server in a manner that allows those
changes to be reverted or replayed (in conjunction with the
extract-data-recovery-log-changes tool) if data recovery is
needed.
|
|
JDBC-based Access Log |
Stores access log information using a JDBC database connection. Disabled by
default. |
|
File-based Access Logs |
Provides a character-based stream used by TextWriter Publishers as a target
for outputting log records. There are six types of file-based loggers:
-
Admin Alert Access Log. Generates administrative alerts for any
operations that match the criteria for this access logger. Disabled by
default.
-
File-based Access Log. Publishes access log messages to the
file system. Enabled by default.
-
Syslog-based Access Log. Publishes access log messages to a syslogd
port. Disabled by default.
-
Expensive-Operations Access Log. Publishes only those access log
messages of operations that take longer than 1000 milliseconds. Disabled by
default.
-
Failed-Operations Access Log. Publishes only those access log
messages of operations that failed for any reason. Enabled by default.
-
Successful Searches with No Entries Returned Log. Publishes only
those access log messages of search operations that failed to return any
entries. Disabled by default.
- JSON Access Logger. Publishes JSON-formatted access log
messages to the file system.
- Console JSON Access Logger. Publishes JSON-formatted access
log messages to the JVM's standard output or standard error stream.
This log publisher is only recommended when the server is run in
no-detach mode and is best suited for use in Docker or other
containers that can capture log content written to standard output
or standard error.
- Third-Party Access Log Publisher. Publishes access log
messages using a custom log publisher created using the Server
SDK.
- Third-Party File-Based Access Log Publisher. Publishes
access log messages to a file using a custom log publisher created
using the Server SDK, including enhanced support for log file
rotation and retention.
|
|
HTTP Operation Log Publisherrs |
- Common Log File HTTP Operation Log Publisher. Publishes
information about HTTP requests in the W3C common log format.
- HTTP Detailed Access. Publishes detailed information about
HTTP requests processed by the server.
|
Debug |
Provides information about warnings, errors, or
significant events that occur within the server. |
|
Debug Loggers |
- Debug ACI Logger. Stores debug information on ACI
evaluation for any request operations against the server.
- Server SDK Extension Debug Logger — Provides simplified
access to debug messages generated by Server SDK extension
|
|
File-based Error Logs |
There are two types of File-based Error Logs:
-
Error log. Publishes error messages to the file system. Enabled by
default.
-
Replication log. Publishes replication error messages to the
file system. Enabled by default.
- JSON Error Logger. Publishes JSON-formatted error log
messages to the file system.
- Console JSON Access Logger. Publishes JSON-formatted access
log messages to the JVM's standard output or standard error stream.
This log publisher is only recommended when the server is run in
no-detach mode and is best suited for use in Docker or other
containers that can capture log content written to standard output
or standard error.
- Third-Party Error Log Publisher. Publishes error log
messages using a custom log publisher created using the Server
SDK.
- Third-Party File-Based Error Log Publisher. Publishes error
log messages to a file using a custom log publisher created using
the Server SDK, including enhanced support for log file rotation
and retention.
|
|
JDBC-based Error Logs |
Stores error log information using a JDBC database connection. Disabled by
default. |
|
Syslog-based Error Logs |
Publishes error messages to a syslogd port. |