HPEL log configuration settings
Configure High Performance Extensible Logging (HPEL) log settings.
We can only access this page when the server is configured to use HPEL log and trace mode.
From the admin console, click...
-
Troubleshooting > Logs and trace > server > Configure HPEL logging
Directory path
Directory to which log files are written. A subdirectory, logdata, is created in this directory, and the log files are written to this location.
This path cannot be shared between servers. The server creates a file with a .owner extension to help detect when two or more servers happen to be trying to use the same path for HPEL output.
Enable log record buffering
The logging system avoids writing to disk each time a log record is created. The logging system creates a buffer that can hold a number of log records, and writes the buffered events when the buffer is full. The logging system also writes the buffered events after a few seconds have passed, even if the buffer is not full.
Select this setting significantly improves logging performance; however, if the server stops unexpectedly, the contents might not be written to the log repository.
Enable log record buffering in almost all cases. Only disable log record buffering when the server is failing unexpectedly and cannot write buffered content to disk before stopping. bprac
Start new log file daily at <time>
Enables the logging framework to close the log file and start a new file at the specified time of day. Closing the file makes it easy to copy the file to an archive.
To automatically archive the log files, set up the backup program to copy files after the time we configured for new logs to be started. Configure the backup to occur at least 10 minutes after the time configured for new logs to be started to ensure that the server has closed the previous file.bprac
Begin cleanup of oldest records
Log cleanup settings to be used to automatically purge the oldest log records, or log records that no longer fit in the configured space, from the log repository.
Select When log size approaches maximum to configure automatic log file cleanup to begin when the total size of the log repository approaches the configured maximum size.
Select When oldest records reach age limit to configure automatic log file cleanup to begin when log content is the age limit specified.
Select When either age or size restriction is met to configure automatic log file cleanup to begin when either of the previous conditions is met.
Regardless of the selection chosen, records are deleted from the log repository in the order in which they were written to the log repository.
Log record age limit
Lifespan, in hours, that log records can remain in the log repository before the log records can be automatically deleted by the server. When the oldest records in the log repository have existed longer than the age limit specified, then those records are targeted for deletion by the server.
Maximum log size
Maximum total size, in megabytes, that the server allows the log repository to reach. When the log repository approaches this size limit, the server deletes the oldest records from the log repository to make space for new log records.
Out of space action
Specifies how the server reacts to an inability to add content to the log repository.
Select Stop server to specify that the server stops when the server is unable to write to the log repository.
Select Purge old records to specify that the server continues to run, and that the oldest log records are immediately removed when the server is unable to write to the log repository.
Select Stop logging to specify that the server continues to run, but that the server cannot continue to write to the log when the server is unable to write to the log repository.
Save runtime changes to configuration as well
That changes are made to both the dynamic state of the running server, and the server configuration, which takes effect on the next restart. If this check box is not selected, the server does not copy the settings into the server configuration.