Create a LogGroupRule. Basically you define what logger name(s) match for this group, what level should be used what logger type (where to log) and what format to write in. If the loggerType is custom, then the callBackLogger must be supplied as callback function to return a custom logger.
Regular expression, what matches for your logger names for this group
LogLevel
LogFormat
Type of logger, if Custom, make sure to implement callBackLogger and pass in, this will be called so you can return your own logger.
Callback function to return a new clean custom logger (yours!)
Get the formatterLogMessage function, see comment on the setter.
Set the default formatterLogMessage function, if set it is applied to all type of loggers except for a custom logger. By default this is null (not set). You can assign a function to allow custom formatting of a log message. Each log message will call this function then and expects your function to format the message and return a string. Will throw an error if you attempt to set a formatterLogMessage if the LoggerType is custom.
The formatter function, or null to reset it.
Generated using TypeDoc
Defines a LogGroupRule, this allows you to either have everything configured the same way or for example loggers that start with name model. It allows you to group loggers together to have a certain loglevel and other settings. You can configure this when creating the LoggerFactory (which accepts multiple LogGroupRules).