Provides beautiful console logging for Ruby applications. Implements fast, buffered log output.
When Ruby decided to reverse the order of exception backtraces, I finally gave up using the built in logging and decided restore sanity to the output of my programs once and for all!
- Thread safe global logger with per-fiber context.
- Carry along context with nested loggers.
- Enable/disable log levels per-class.
- Detailed logging of exceptions.
- Beautiful logging to the terminal or structured logging using JSON.
Please see the project documentation for more details.
-
Getting Started - This guide explains how to use
consolefor logging. -
Command Line - This guide explains how the
consolegem can be controlled using environment variables. -
Integration - This guide explains how to integrate the
consoleoutput into different systems. -
Events - This guide explains how to log structured events with a well-defined schema.
Please see the project releases for all releases.
- Always return
nilfromConsole::Filterlogging methods.
- Fix logging
exception:keyword argument when the value was not an exception.
- Don't make
Kernel#warnredirection toConsole.warnthe default behavior, you mustrequire 'console/warn'to enable it. - Remove deprecated
Console::Logger#failure. - Consistent Handling of Exceptions
- Add support for
Kernel#warnredirection toConsole.warn.
We welcome contributions to this project.
- Fork it.
- Create your feature branch (
git checkout -b my-new-feature). - Commit your changes (
git commit -am 'Add some feature'). - Push to the branch (
git push origin my-new-feature). - Create new Pull Request.
In order to protect users of this project, we require all contributors to comply with the Developer Certificate of Origin. This ensures that all contributions are properly licensed and attributed.
This project is best served by a collaborative and respectful environment. Treat each other professionally, respect differing viewpoints, and engage constructively. Harassment, discrimination, or harmful behavior is not tolerated. Communicate clearly, listen actively, and support one another. If any issues arise, please inform the project maintainers.
