Implementors are notified of backup file compression after the compression is complete.
Implementors are notified of a file roll after the roll is complete.
Responsible for periodically sampling the number of log files with a given base filename and time-based extension, and for deleting the older files if the scavenger's conditions are met.
An object that executes submitted logging tasks that provides methods to manage termination and methods that can produce a
Responsible for periodically sampling the number of log files with a given base filename and time-based extension, and for deleting the older files if the minimum specified space remains available on the filesystem.
Base class for roller implementations, this has responsibility only for performing the actual file roll.
Configuration properties used by the
Composes the behaviour of the startup roller, file-size roller, and the time-based roller.
Responsible for periodically sampling the number of log files with a given base filename and time-based extension, and for deleting the older files if the file count limit is exceeded.
This event is fired after a log backup file has been compressed.
Has responsibility only for performing the actual file roll.
This event is fired after the current log file has been renamed as a backup and a new file already opened for logging.
Responsible for deciding whether a file roll should take place based upon file size limits, and for performing a file roll if necessary.
Provides support for processing
Responsible for providing compression strategy instances (via factory methods), implementing template methods used by specific strategies, and the creation of compressed backup files.
Responsible for compressing log files using a given compression algorithm, adding checksums if specified.
Responsible for listing, sorting, and filtering log file lists.
This appender is responsible for writing log events to file, and rolling files when they reach configurable limits of time and/or size.
Responsible for ensuring that log files are rolled pro-actively when rollover is due.
Responsible for rolling at a logging time boundary, as configured by a date pattern.
Responsible for selecting the appropriate time-based rolling strategy at start-up, based upon the contents of the Appender's DatePattern property; also responsible for computing the next roll time.
Responsible for encapsulating time-oriented operations on log filenames or partial log filenames via the concatenation methods.