Action must be taken immediately.
Example: Entire website down, database unavailable, etc. This should trigger the SMS alerts and wake you up.
The message to log
The context data to use with the message
Critical conditions.
Example: Application component unavailable, unexpected exception.
The message to log
The context data to use with the message
Detailed debug information.
The message to log
The context data to use with the message
System is unusable.
The message to log
The context data to use with the message
Runtime errors that do not require immediate action but should typically be logged and monitored.
The message to log
The context data to use with the message
Create the implementation of this specific logger
The level of the log entry
The message to log
Interesting events.
Example: User logs in, SQL logs.
The message to log
The context data to use with the message
Method to handle interpolation to recursively combine a context with a message. Usually this is done directly with javascript. However, there maybe times when a piece of code would smell better using this version of interpolation.
The message to use in the interpolation
The context data to use with the message
Logs with an arbitrary level.
The level of the log entry
The message to log
The context data to use with the message
Normal but significant events.
The message to log
The context data to use with the message
Exceptional occurrences that are not errors.
Example: Use of deprecated APIs, poor use of an API, undesirable things that are not necessarily wrong.
The message to log
The context data to use with the message
Generated using TypeDoc
Abstract class definition for the creating custom loggers where the developer only has to handle the implementation
Inspired by PSR-3 created by the PHP-FIG team. Thanks!!