Wrap Logging::Logger with ActiveSupport::TaggedLogging

[sshaw]

By default Rails.logger is wrapped. When migrating to logging-rails I usually end up doing this. Any reason not to do this in the initializer?

[TwP]

Logging provides the nested diagnostic context that does exactly this. You can also used the mapped diagnostic context to attach named attributes to each log message.

Logging.ndc.push("fact1") {
  logger.info("some message")
}

You can also nest these contexts. The block format is optional (although convenient).

Logging.ndc.push("fact1")
# lots of other code
Logging.ndc.push("fact2") {
  logger.info("another message")
}
# and even more code
Logging.ndc.pop

[sshaw]

Logging provides the nested diagnostic context that does exactly this. You can also used the mapped diagnostic context

Yes, I'm familiar with these, but why force one to cook up something custom
just to get what Rails provides out of the box by assigning Procs or Symbols to config.log_tags?

Of course it's trivial for one to wrap Logging::Logger with ActiveSupport::TaggedLogging, but
this is logging-rails. It should integrate logging with Rails' features, not the other way around 😸

[sshaw]

Though there is one thing to note: Rails will wrap all loggers (ActiveRecord, ActionController, etc...)