Search Results for "string"

...Installation is done using the npm install command. Create a new morgan logger middleware function using the given format and options. The format argument may be a string of a predefined name, a string of a format string, or a function that will produce a log entry. The format function will be called with three arguments tokens, req, and res, where tokens is an object with all defined tokens, req is the HTTP request and res is the HTTP response. The function is expected to return a string that will be the log line, or undefined / null to skip logging. ...

...The LoggerInterface exposes eight methods to write logs to the eight RFC 5424 levels (debug, info, notice, warning, error, critical, alert, emergency). Every method accepts a string as the message, or an object with a toString() method. Implementors MAY have special handling for the passed objects. If that is not the case, implementors MUST cast it to a string. The interfaces and classes described as well as relevant exception classes and a test suite to verify your implementation are provided as part of the psr/log package. ...

Flogger is a structured logging API for Java that decouples how you log from where logs ultimately go, making it easy to change backends without rewriting application code. Instead of building messages eagerly, it uses lazy parameter evaluation so expensive string building only happens when a log statement is actually emitted. The API encourages structured key–value context and fine-grained rate limiting, which helps keep logs informative without flooding systems during high-traffic or error storms. Handlers (backends) can route the same log record to multiple destinations—console, files, cloud logging—while preserving structured fields for search and alerting. ...

...LogEngine2 can load loggers from .lfg file. Examples of .lfg files are included into bundle. LogEngine2 provides various log targets: regular files, rotating log files, console logging, string stream, user custom function. Log line format is easy configurable.

...By utilizing the secrets option, secrets and other sensitive information can be filtered out from the body as well as the metadata, i.e. scope names etc, of to-be-logged messages. The option is part of the configuration object passed to a Signale instance on its initialization, and is of type Array<String|Number>. The array can hold multiple secrets, all of which are removed, if present, from the to-be-logged messages and are replaced with the default '[secure]' string.