What's this?
MrLogaLoga is a logger for Ruby that allows you to easily attach contextual information to your log messages. When writing logs, messages only tell half the story. MrLogaLoga allows you to make the most of your logs.
logger.info('message', user: 'name', data: 1)
# I, [2022-01-01T12:00:00.000000 #19074] INFO -- Main: message user=user data=1
You can find out more about the motivation behind the project here. For usage read Usage or Advanced Usage
Note: This gem is in early development. Try it out and leave some feedback, it really goes a long way in helping me out with development. Any feature request or bug report is welcome. If you like this project, leave a star to show your support! ⭐
Getting Started
Add this line to your application's Gemfile:
gem 'mr_loga_loga'
And then execute:
bundle install
Usage
MrLogaLoga provides the same interface as the Ruby default logger you are used to. In addition, however, you can attach contextual information to your log messages.
require 'mr_loga_loga'
logger = MrLogaLoga::Logger.new
logger.info('message', user: 'name', data: 1)
# I, [2022-01-01T12:00:00.000000 #19074] INFO -- Main: message user=user data=1
logger.context(class: 'classname').warn('message')
# W, [2022-01-01T12:00:00.000000 #19074] WARN -- Main: message class=classname
To customize how log messages are formatted see [Formatters][#formatters].
Advanced Usage
MrLogaLoga provides a fluent interface to build log messages. For example, to attach an additional user
field to a log message you can use any of the following:
logger.info('message', user: 'name')
logger.context(user: 'name').info('message') # Explicit context
logger.context { { user: 'name' } }.info('message') # Block context
logger.user('name').info('message') # Dynamic context method
logger.user { 'name' }.info('message') # Dynamic context block
The block syntax is recommended when logging calculated properties . You can find more in-depth information about specific method in the Code Documentation.
Shared Context
If multiple log messages within the same class should share a context include the MrLogaLoga
module. Using logger
will result in the defined context being included per default:
class MyClass
include MrLogaLoga
# This is the default. You may overwrite this in your own classes
def loga_context
{ class_name: self.class.name }
end
def log
# This includes the class name in the log message now
logger.debug('debug') # debug class_name=MyClass
# Additional context will be merged
logger.debug('debug', user: 'user') # debug class_name=MyClass user=user
end
end
When used with Rails logger will default to Rails.logger
. If you use MrLogaLoga outside of Rails, you can either configure the logger instance to be used globally, or by overwriting the loga_loga
method:
# In some configuration class
MrLogaLoga.configure do |configuration|
logger = MrLogaLoga::Logger.new($stdout)
end
# In the class where you do the logging itself
class MyClass
include MrLogaLoga
def loga_loga
MrLogaLoga::Logger.new($stdout)
end
def log
# ...
end
end
Formatters
MrLogaLoga uses the KeyValue formatter per default. The Json formatter is also included. To use a specific formatter pass it to the logger constructor:
MrLogaLoga::Logger.new(STDOUT, formatter: MrLogaLoga::Formatters::KeyValue.new)
You can implement and add your own formatters like so:
class MyFormatter
def call(severity, datetime, progname, , context)
context = context.map { |key, value| "#{key}=#{value}" }.compact.join(' ')
"#{severity} #{datetime.strftime('%Y-%m-%dT%H:%M:%S.%6N')} #{progname} #{} #{context}"
end
end
MrLogaLoga::Logger.new(STDOUT, formatter: MyFormatter.new)
Rails
Using MrLogaLoga in Ruby on Rails is straightforward. Set up MrLogaLoga as logger in your application.rb
or environment files and you are off to the races:
# application.rb
config.logger = MrLogaLoga::Logger.new(STDOUT)
config.log_level = :info
Note that setting config.log_formatter
does not work. You must set the formatter in the logger constructor as described in Formatters.
Lograge
LogRage and MrLogaLoga work well together. When using both gems Lograge will be patched so that data will be available as context
in MrLogaLoga. Make sure that MrLogaLoga is required after Lograge:
gem 'lograge'
gem 'mr_loga_loga'
Note that Lograge's formatters won't be used. Use MrLogaLoga's own formatters instead.
Why MrLogaLoga?
The more context your logs provide, the more use you will get out of them. The standard Ruby logger only takes a string as an argument, so you have to resort to something like this:
logger.debug("my message user=#{user} more_data=#{data}")
This is fine, as long as you do not need to change your log format. Changing your log formatter will not change the format of your message, nor the formatting of the contextual information you provided.
MrLogaLoga addresses this by allowing you to attach contextual information to your logs and giving you full control over how both message and context are formatted. There are other gems doing similar things, most notably Semantic Logger. Where Semantic Logger provides lots of functionality related to logging, MrLogaLoga focuses on making it nice to write log messages - and nothing more.
Credit
This little library was inspired by Lograge first and foremost. I would like to thank the amazing @LenaSchnedlitz for the incredible logo! 🤩
Development
After checking out the repo, run bin/setup
to install dependencies. Then, run rake
to run the tests and linter. You can also run bin/console
for an interactive prompt that will allow you to experiment.
To install this gem onto your local machine, run bundle exec rake install
. To release a new version, update the version number in version.rb
, and then run bundle exec rake release
, which will create a git tag for the version, push git commits and the created tag, and push the .gem
file to rubygems.org.
Contributing
Thank you for contributing! :heart:
We welcome all support, whether on bug reports, code, design, reviews, tests, documentation, translations, or just feature requests.
Please use GitHub issues to submit bugs or feature requests.
License
The gem is available as open-source under the terms of the MIT License.
Code of Conduct
Everyone interacting in the MrLogaLoga project's codebases, issue trackers, chat rooms, and mailing lists is expected to follow the code of conduct.