get_log_levels

log_levels

log_level

add_log_levels

remove_log_levels

a named <code>character</code> vector (see examples)

levels

a <code>character</code> vector of the names of the levels to remove

level_names

Display, add and remove character labels for log levels.

A flexible, feature-rich yet light-weight logging
framework based on 'R6' classes. It supports hierarchical loggers,
custom log levels, arbitrary data fields in log events, logging to
plaintext, 'JSON', (rotating) files, memory buffers, and databases, as
well as email and push notifications. For a full list of features with
examples please refer to the package vignette.

Stefan Fleck

A Fully Featured Logging Framework

get_log_levels function

lgr comes with the following predefined log levels that are identical to
the log levels of log4j.<table><tr><td>
Level </td>
<td> Name </td>
<td> Description </td>
</tr><tr><td>
<code>0</code> </td>
<td> off </td>
<td> A log level of 0/off tells a Logger or Appender to suspend all logging </td>
</tr><tr><td>
<code>100</code> </td>
<td> fatal </td>
<td> Critical error that leads to program abort. Should always indicate a <code>stop()</code> or similar </td>
</tr><tr><td>
<code>200</code> </td>
<td> error </td>
<td> A severe error that does not trigger program abort</td>
</tr><tr><td>
<code>300</code> </td>
<td> warn </td>
<td> A potentially harmful situation, like <code>warning()</code></td>
</tr><tr><td>
<code>400</code> </td>
<td> info </td>
<td> An informational message on the progress of the application</td>
</tr><tr><td>
<code>500</code> </td>
<td> debug </td>
<td> Finer grained informational messages that are mostly useful for debugging</td>
</tr><tr><td>
<code>600</code> </td>
<td> trace </td>
<td> An even finer grained message than debug</td>
</tr></table>

get_log_levels: Manage Log Levels

Description

Usage

Arguments

Value

Default Log Levels

Examples

Level	Name	Description
`0`	off	A log level of 0/off tells a Logger or Appender to suspend all logging
`100`	fatal	Critical error that leads to program abort. Should always indicate a `stop()` or similar
`200`	error	A severe error that does not trigger program abort
`300`	warn	A potentially harmful situation, like `warning()`
`400`	info	An informational message on the progress of the application
`500`	debug	Finer grained informational messages that are mostly useful for debugging
`600`	trace	An even finer grained message than debug