KO | EN

GitLite

Minimalist Open Source Repository Search Engine

gitlite — search

#dsh #dsh-plugin #developer-tools #ai-agent #claude-code #codex #typescript #ai-agents #deepseek-harness #mcp #cli #rust

log-warper

★ 18 Open GitHub ↗

Logging library to provide more convenient, extremely configurable but simple monadic interface with pretty output

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

log-warper
==========

[![Build Status](https://travis-ci.org/serokell/log-warper.svg)](https://travis-ci.org/serokell/log-warper)
[![Hackage](https://img.shields.io/hackage/v/log-warper.svg)](https://hackage.haskell.org/package/log-warper)
[![Stackage LTS](http://stackage.org/package/log-warper/badge/lts)](http://stackage.org/lts/package/log-warper)
[![Stackage Nightly](http://stackage.org/package/log-warper/badge/nightly)](http://stackage.org/nightly/package/log-warper)
[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)

`log-warper` is a high level and featureful logging library with monadic interface.

You can jump right into [introduction tutorial](https://github.com/serokell/log-warper/blob/master/examples/HowTo.md)
to see how to write logging with `log-warper`.

## Features

Here is the list of features `log-warper` provides.

1. Hierarchical logger names.

Logger names (tags for loggers) form hierarchy. It means, that `""`
   (also known as `mempty` or `rootLoggerName`) is a parent of logger with name `"node"` which is
   a parent of logger with name `"node.communication"`. So, logger name comprises dot-separated components.
   This means that if some logger name doesn't have some settings (like severity or output file) it takes
   its settings from the closest parent, containing this settings.

2. Logging initialization from `.yaml` configuration file.

Whole logging configuration can be specifed in a single `.yaml` file.
   See [example here](https://github.com/serokell/log-warper/blob/c1df47e70c48bae62ff81a11fea0b45d50c172e7/logger-config-example.yaml).

3. Monadic logging interface.

`log-warper` uses `mtl`-style type classes to provide monadic interfaces for logging.

4. Strict `StateT` based pure logging.

See [this tutorial](https://github.com/serokell/log-warper/blob/master/examples/PureLogging.md)
   on pure logging with `log-warper`.

5. Different severity levels of messages with the ability to configure `Set` of severities.

6. Output is colored :star:

When you log messages, you see time of this logging message, logger name, severity and `ThreadId`.
   Message formatting is configurable. Color or logged message tag depends on `Severity` for this message.

7. Flexible and easy creation of `LoggerConfig` using monoidal builders and lenses.

In case `.yaml` configuration is not enough for you, you can use `lens`-based EDSL to create configurations.
   `LoggerConfig` also implements instances for `Semigroup` and `Monoid` so you can combine your configurations
   from different sources (CLI and `.yaml` for example).

8. Logger rotation.

`log-warper` supports logger rotation. Yes, there exist `logrotate` and similar tools.
   But it's not easy to configure cross-platform (Windows, Linux, OSX) logging rotation with external tools.

9. Ability to acquire last `N` megabytes of logs from in-memory cache.

In case you want to analyze logging messages you can take them from in-memory cache.

## Reference guide (FAQ)

Here you can find hints and tips how to achieve desired behavior with `log-warper`.

1. How can I redirect all output to stderr?

* Write `termSeveritiesErr: All` on top-level of your `.yaml` file.

2. How can I disable only Error messages for my logger?

* Use [`excludeError`](https://hackage.haskell.org/package/log-warper-1.8.5/docs/System-Wlog-Severity.html#v:excludeError) function.

3. How can I show `ThreadId` inside log message?

* Add `showTid: true` to your `.yaml` file.

4. How to easily disable terminal output?

* Put these lines into `.yaml` file:

```
   termSeveritiesOut : []
   termSeveritiesErr : []
   ```

5. How can I enable messages with severity `Info` and higher?

* Write `severity: Info+` inside tree node of your logger settings.

6. How can I log inside functions like `forkIO`?

* Use [`liftLogIO`](https://hackage.haskell.org/package/log-warper-1.8.5/docs/System-Wlog-CanLog.html#v:liftLogIO) function.
   Its Haddock contains nice usage example.

7. How can I easily log exceptions without throwing them?

* Use functions from [`System.Wlog.Exceptions`](https://hackage.haskell.org/package/log-warper-1.8.5/docs/System-Wlog-Exception.html) module.

## Contributing

> **This project uses [`universum`](https://github.com/serokell/universum)
> as default prelude**

log-warper

Explore Similar Repositories

Was this content helpful?

Recent Feedback

Download README