Network Deployment (Distributed operating systems), v8.0 > Reference > Log and trace file descriptions
HPEL log configuration settings
Use this page to configure High Performance Extensible Logging settings.
This page is accessible only when the server is configured to use HPEL.
From the console...
Troubleshooting > Logs and trace > server_name
> Configure HPEL logging .
Change to HPEL logging and tracing from basic mode
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. Enable log record buffering 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.
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 your server is failing unexpectedly and cannot write buffered content to disk before stopping. bprac
Start new log file daily at <time> Enable 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 your log files, set up your backup program to copy files after the time you 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.
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.
To configure automatic log file cleanup to begin when log content is the age limit specified.
When oldest records reach age limit
To configure automatic log file cleanup to begin when either of the previous conditions is met.
When either age or size restriction is met
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 How the server reacts to an inability to add content to the log repository.
To specify that the server stops when the server is unable to write to the log repository.
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.
Purge old records
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 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.