Public Member Functions
	RepeatGuardLogger (AcsLogger logger, long interval, TimeUnit timeUnit, int maxRepetitions)
void	log (Level level, String message)
void	log (Level level, String message, Throwable thr)
boolean	isLoggingEnabled ()
Static Public Member Functions
static RepeatGuardLogger	createTimeBasedRepeatGuardLogger (AcsLogger logger, long interval, TimeUnit timeUnit)
static RepeatGuardLogger	createCounterBasedRepeatGuardLogger (AcsLogger logger, int maxRepetitions)
Protected Attributes
final RepeatGuard	guard

Detailed Description

This class wraps a logger so that logging of records is skipped until a given number of logging attempts or given time has passed. It is based on RepeatGuard. Typically you want to create one RepeatGuardLogger for each guarded kind of log message (= logging line in your code). Only if you want to control the repetition of different kinds of log messages (at different places in your code) using the same counter and timer (which could mean that one kind of log may always be suppressed while another type may always be logged) then you should reuse one instance of this class for different lines of logging in your code.

There seems to be no real use case for passing different loggers to one repeat guard, even though this was described in the original design. Therefore we plan to remove log(Logger, Level, String) and logAndIncrement(Logger, Level, String) in the future. If you feel they are useful (because you have a case where the logger cannot or should not be passed in the constructor) then we can keep these methods as alternatives to the recommended passing of the logger in the constructor. Please report this to ACS.

Constructor & Destructor Documentation

alma.acs.logging.RepeatGuardLogger.RepeatGuardLogger	(	AcsLogger	logger,
		long	interval,
		TimeUnit	timeUnit,
		int	maxRepetitions
	)

Constructor for a time and counter based repeat guard logger.

If only time or counter should apply, but not both together, it is better to use the factory methods createTimeBasedRepeatGuardLogger(AcsLogger, long, TimeUnit) or createCounterBasedRepeatGuardLogger(AcsLogger, int). However it is also possible to use negative values for the quantities that should not be considered.

Parameters:

	logger	The logger to be used in
	interval	Time interval (in `timeUnit` units).
	timeUnit	Time unit of `interval` parameter.
	maxRepetitions	Maximum number of skipped repetitions.

Exceptions:

IllegalArgumentException

if interval <= 0 && maxRepetitions <= 0

References alma.acs.logging.AcsLogger.addLoggerClass(), and alma.acs.logging.RepeatGuardLogger.guard.

Referenced by alma.acs.logging.RepeatGuardLogger.createCounterBasedRepeatGuardLogger(), and alma.acs.logging.RepeatGuardLogger.createTimeBasedRepeatGuardLogger().

Member Function Documentation

static RepeatGuardLogger alma.acs.logging.RepeatGuardLogger.createCounterBasedRepeatGuardLogger	(	AcsLogger	logger,
		int	maxRepetitions
	)			`[static]`

Factory method for a repeat guard logger which only uses a counter of skipped logs, regardless of the time passed since the last log.

Exceptions:

IllegalArgumentException

if maxRepetitions <= 0

See also:: RepeatGuardLogger(AcsLogger, long, TimeUnit, int)

References alma.acs.logging.RepeatGuardLogger.RepeatGuardLogger().

static RepeatGuardLogger alma.acs.logging.RepeatGuardLogger.createTimeBasedRepeatGuardLogger	(	AcsLogger	logger,
		long	interval,
		TimeUnit	timeUnit
	)			`[static]`

Factory method for a repeat guard logger which only uses a timer, regardless of the number of skipped logs.

Exceptions:

IllegalArgumentException

if interval <= 0

See also:: RepeatGuardLogger(AcsLogger, long, TimeUnit, int)

References alma.acs.logging.RepeatGuardLogger.RepeatGuardLogger().

boolean alma.acs.logging.RepeatGuardLogger.isLoggingEnabled ( )

Checks if the internal repeat guard allows a log. This method is an alternative to the various log methods to be used if

You want the repeat guard to skip or enable different log messages together (all or none).
You want to use specialized methods of the guarded Logger, such as Logger#log(java.util.logging.LogRecord), which are not exposed by this RepeatGuardLogger

In either of these cases, simply surround a call to the normal logger with an
if (isLoggingEnabled()) {myLogger.blabla}.

The internal log counter (if present) will be incremented the same way as for one call to, say, log(Level, String)}.

Note that you might be better off using RepeatGuard directly if this method is the only one you need from this RepeatGuardLogger. Using this method makes sense though for a mix of logs, some to be made via the RepeatGuardLogger.log methods, and others directly via the logger surrounded by a call to this isLoggingEnabled

Returns:: true if the counter/timer allows a log message (or a batch of log messages that must appear together)

References alma.acs.logging.RepeatGuard.checkAndIncrement(), and alma.acs.logging.RepeatGuardLogger.guard.

void alma.acs.logging.RepeatGuardLogger.log	(	Level	level,
		String	message
	)

Logs the message at the given level, unless the internal RepeatGuard prevents this based on the timer and/or log record counter. If a log record counter is active, it will be advanced, which corresponds to RepeatGuard#checkAndIncrement(). (Note that following the same terminology as RepeatGuard, this method would have to be called logAndIncrement; it is simply called log though because here we don't support the variant of having a counter enabled without using it.)