File Based Error Log Publisher

File Based Error Log Publishers publish error messages to the file system.

Parent

The File Based Error Log Publisher object inherits from Error Log Publisher.

Dependencies

File Based Error Log Publishers depend on the following objects:

Properties

Use the --advanced option to access advanced properties.

Basic Properties

append

SynopsisSpecifies whether to append to existing log files.
Default Valuetrue
Allowed Valuestrue
false
Multi-valuedNo
RequiredNo
Admin Action RequiredNone
AdvancedNo
Read-OnlyNo

default-severity

SynopsisSpecifies the default severity levels for the logger.
Default Valueerror
warning
Allowed Values

all: Messages of all severity levels are logged.

debug: The error log severity that is used for messages that provide debugging information triggered during processing.

error: The error log severity that is used for messages that provide information about errors which may force the server to shut down or operate in a significantly degraded state.

info: The error log severity that is used for messages that provide information about significant events within the server that are not warnings or errors.

none: No messages of any severity are logged by default. This value is intended to be used in conjunction with the override-severity property to define an error logger that will publish no error message beside the errors of a given category.

notice: The error log severity that is used for the most important informational messages (i.e., information that should almost always be logged but is not associated with a warning or error condition).

warning: The error log severity that is used for messages that provide information about warnings triggered during processing.

Multi-valuedYes
RequiredNo
Admin Action RequiredNone
AdvancedNo
Read-OnlyNo

enabled

SynopsisIndicates whether the Log Publisher is enabled for use.
Default ValueNone
Allowed Valuestrue
false
Multi-valuedNo
RequiredYes
Admin Action RequiredNone
AdvancedNo
Read-OnlyNo

log-file

SynopsisThe file name to use for the log files generated by the File Based Error Log Publisher .
DescriptionThe path to the file is relative to the server root.
Default ValueNone
Allowed ValuesA string.
Multi-valuedNo
RequiredYes
Admin Action RequiredThe object must be disabled and re-enabled for changes to take effect.
AdvancedNo
Read-OnlyNo

log-file-permissions

SynopsisThe UNIX permissions of the log files created by this File Based Error Log Publisher .
Default Value640
Allowed ValuesA valid UNIX mode string. The mode string must contain three digits between zero and seven.
Multi-valuedNo
RequiredYes
Admin Action RequiredNone
AdvancedNo
Read-OnlyNo

override-severity

SynopsisSpecifies the override severity levels for the logger based on the category of the messages.
DescriptionEach override severity level should include the category and the severity levels to log for that category, for example, core=error,info,warning. Valid categories are: core, extensions, protocol, config, log, util, schema, plugin, jeb, backend, tools, task, access-control, admin, sync, version, quicksetup, admin-tool, dsconfig, user-defined. Valid severities are: all, error, info, warning, notice, debug.
Default ValueAll messages with the default severity levels are logged.
Allowed ValuesA string in the form category=severity1,severity2...
Multi-valuedYes
RequiredNo
Admin Action RequiredNone
AdvancedNo
Read-OnlyNo

retention-policy

SynopsisThe retention policy to use for the File Based Error Log Publisher .
DescriptionWhen multiple policies are used, log files will be cleaned when any of the policy's conditions are met.
Default ValueNo retention policy is used and log files will never be cleaned.
Allowed ValuesThe name of an existing Log Retention Policy.
Multi-valuedYes
RequiredNo
Admin Action RequiredNone
AdvancedNo
Read-OnlyNo

rotation-policy

SynopsisThe rotation policy to use for the File Based Error Log Publisher .
DescriptionWhen multiple policies are used, rotation will occur if any policy's conditions are met.
Default ValueNo rotation policy is used and log rotation will not occur.
Allowed ValuesThe name of an existing Log Rotation Policy.
Multi-valuedYes
RequiredNo
Admin Action RequiredNone
AdvancedNo
Read-OnlyNo

Advanced Properties

asynchronous

SynopsisIndicates whether the File Based Error Log Publisher will publish records asynchronously.
Default Valuefalse
Allowed Valuestrue
false
Multi-valuedNo
RequiredYes
Admin Action RequiredNone
AdvancedYes
Read-OnlyNo

auto-flush

SynopsisSpecifies whether to flush the writer after every log record.
DescriptionIf the asynchronous writes option is used, the writer will be flushed after all the log records in the queue are written.
Default Valuetrue
Allowed Valuestrue
false
Multi-valuedNo
RequiredNo
Admin Action RequiredNone
AdvancedYes
Read-OnlyNo

buffer-size

SynopsisSpecifies the log file buffer size.
Default Value64kb
Allowed ValuesA positive integer representing a size. Lower limit: 1.
Multi-valuedNo
RequiredNo
Admin Action RequiredNone
AdvancedYes
Read-OnlyNo

java-class

SynopsisThe fully-qualified name of the Java class that provides the File Based Error Log Publisher implementation.
Default Valueorg.opends.server.loggers.TextErrorLogPublisher
Allowed ValuesA Java class that extends or implements:
org.opends.server.loggers.LogPublisher
Multi-valuedNo
RequiredYes
Admin Action RequiredNone
AdvancedYes
Read-OnlyNo

queue-size

SynopsisThe maximum number of log records that can be stored in the asynchronous queue.
Default Value5000
Allowed ValuesAn integer. Lower limit: 1.
Multi-valuedNo
RequiredNo
Admin Action RequiredNone
AdvancedYes
Read-OnlyNo

time-interval

SynopsisSpecifies the interval at which to check whether the log files need to be rotated.
Default Value5s
Allowed ValuesA duration. Lower limit: 1 milliseconds.
Multi-valuedNo
RequiredNo
Admin Action RequiredNone
AdvancedYes
Read-OnlyNo