org.das2.util.LoggerManager

Central place that keeps track of loggers. Note that both org.das.datum and org.das2.datum have this same class, which is there to avoid coupling between the packages.

clearTimer

explicitly remove this timer.

Returns:

See Also:

getLoggers

return the list of known loggers.

Returns:

isEnableTimers

return enableTimers property.

Returns:

isUseTimeTaggingLoggers

are we keeping track of log message times, so we can sort loggers by how recently messages were posted?

Returns:

logExitGuiEvent

call this at the end of the GUI event to measure time to respond.

Parameters

Returns:

logGuiEvent

provide easy way to log all GUI events.

Parameters

Returns:

logPropertyChangeEvent

log property change events. (I realized I spend a lot of time debugging walking through the property change fire event code, and I should just add a log message to all propertyChange codes.)

Parameters

Returns:

markTime

mark the time using the thread name.

Returns:

readConfiguration

A slightly more transparent logging configuration would provide feedback about what configuration file it's loading. This will echo when the configuration file would be. The idea is when you are completely frustrated with not getting the logger to behave, you can add: org.das2.util.LoggerManager.readConfiguration() to your code.

Returns:

resetTimer

reset the timer. The lifecycle is like so:

• LoggerManager.setTimerLogfile("/tmp/mylogfile.txt")
• LoggerManager.resetTimer("big task");
• LoggerManager.markTime("done loading");
• LoggerManager.markTime("calculated data");
• LoggerManager.clearTimer();

Returns:

setEnableTimers

if enableTimers is true, then resetTimer and markTime have an effect. Each thread can have a timer to measure the execution time for a process.

Parameters

Returns:

setTimerLogfile

channel the logging information to here, setEnableTimers(false) to close.

Parameters

Returns:

setUseTimeTaggingLoggers

Parameters

Returns: