💎 ActiveSupport::TaggedLogging::Formatter

if ci_badges.map(&:color).detect { it != "green"} ☝️ let me know on Discord or RubyForum, as I may have missed the notification.

if ci_badges.map(&:color).all? { it == "green"} 👇️ send money so I can do more of this. FLOSS maintenance is now my full-time job.

👣 How will this project approach the September 2025 hostile takeover of RubyGems? 🚑️

I've summarized my thoughts in this blog post.

🌻 Synopsis

Backports the Rails 8 ActiveSupport::TaggedLogging implementation, including tag stacks, formatter support, and compatibility fixes for older supported Rails and Ruby versions.

💡 Info you can shake a stick at

Tokens to Remember
Works with JRuby
Works with Truffle Ruby
Works with MRI Ruby 4
Works with MRI Ruby 3
Support & Community
Source
Documentation
Compliance
Style
Maintainer 🎖️
`...` 💖	🧊 🐙 🛖 🧪

Compatibility

Compatible with MRI Ruby, JRuby, and TruffleRuby. CI workflows and Appraisals are generated for MRI Ruby 3.1.0+. This test floor is configured by ruby.test_minimum in .kettle-jem.yml and may be higher than the gem's runtime compatibility floor when legacy Rubies are not practical for the current toolchain.

The amazing test matrix is powered by the kettle-dev stack.

How kettle-dev manages complexity in tests

Gem	Source	Role
appraisal2	GitHub	multi-dependency Appraisal matrix generation
appraisal2-rubocop	GitHub	RuboCop Appraisal generator integration
kettle-dev	GitHub	development, release, and CI workflow tooling
kettle-jem	GitHub	Appraisals & CI workflow templates
kettle-soup-cover	GitHub	SimpleCov coverage policy and reporting
kettle-test	GitHub	standard test runner and coverage harness
rubocop-lts	GitHub	Ruby-version-aware linting
turbo_tests2	GitHub	parallel test execution

Federated DVCS

Find this repo on federated forges (Coming soon!)

Federated DVCS Repository	Status	Issues	PRs	Wiki	CI
🧪 galtzo-floss/activesupport-tagged_logging on GitLab	The Truth	💚	💚	💚	🐭 Tiny Matrix
🧊 galtzo-floss/activesupport-tagged_logging on CodeBerg	An Ethical Mirror (Donate)	💚	💚	➖	⭕️ No Matrix
🐙 galtzo-floss/activesupport-tagged_logging on GitHub	Another Mirror	💚	💚	💚	💯 Full Matrix

Enterprise Support

Available as part of the Tidelift Subscription.

Need enterprise-level guarantees?

The maintainers of this and thousands of other packages are working with Tidelift to deliver commercial support and maintenance for the open source packages you use to build your applications. Save time, reduce risk, and improve code health, while paying the maintainers of the exact packages you use.

💡Subscribe for support guarantees covering all your FLOSS dependencies
💡Tidelift is part of Sonar
💡Tidelift pays maintainers to maintain the software you depend on!
📊@Pointy Haired Boss: An enterprise support subscription is "never gonna let you down", and supports open source maintainers

Alternatively:

✨ Installation

Install the gem and add to the application's Gemfile by executing:

bundle add activesupport-tagged_logging

If bundler is not being used to manage dependencies, install the gem by executing:

gem install activesupport-tagged_logging

⚙️ Configuration

Load activesupport-tagged_logging before active_support so it can install its compatibility implementation. Configure the logger and tags through the normal Rails/ActiveSupport logger setup; this gem has no separate initializer format.

🔧 Basic Usage

When it doesn't work

NameError: uninitialized constant ActiveSupport::TaggedLogging

The issue is likely that canonical active_support has been loaded before this gem had a chance to load.

This is a common issue, see the following for more context:

https://github.com/soutaro/steep/pull/484
https://github.com/santry/json_tagged_logger/pull/22
https://github.com/VitalConnectInc/rails/pull/1
- Rails itself loads active_support, incorrectly, internally!
- When I get time I want to document this and submit a PR to Rails core.
https://github.com/VitalConnectInc/webpacker/pull/3

This gem has a solution for all of the above, but it only works if this gem is loaded first.

Keep reading below.

With Rails

In a Rails project change config/boot.rb to match:

ENV["BUNDLE_GEMFILE"] ||= File.expand_path("../Gemfile", __dir__)

require "bundler/setup" # Set up gems listed in the Gemfile.

# NOTE: needs to load before active_support, so the magic will work.
require "activesupport-tagged_logging"

require "bootsnap/setup" # Speed up boot time by caching expensive operations.

With Sidekiq

You won't be able to use bundle exec sidekiq, as that results in loading active_support too early. However, you should have a bin/sidekiq binstub, which can be fixed to load activesupport-tagged_logging early!

Change the last few lines of bin/sidekiq to match:

require "rubygems"
require "bundler/setup"

# NOTE: needs to load before active_support, so the magic will work.
#       sidekiq, when loaded in Rails, loads active_job,
#       which depends on active_support, hence this early load hack.
require "activesupport-tagged_logging"

load Gem.bin_path("sidekiq", "sidekiq")

With `activesupport-logger` gem

activesupport-logger is automatically depended on and configured by this gem, so you don't need to do anything else.

IMPORTANT: When using this gem, do not require "activesupport-logger" in your code. Load order matters.

With `activesupport-broadcast_logger` gem

activesupport-broadcast_logger is automatically depended on and configured by this gem, so you don't need to do anything else.

IMPORTANT: When using this gem, do not require "activesupport-broadcast_logger" in your code. Load order matters.

With broadcasting support

If you want to try an experimental fix from a PR, run:

Activesupport::FixPr53105.init

NOTE: The bits of logic that are unique to this gem are in the namespace Activesupport (sic).

See: https://github.com/rails/rails/pull/53105/files

🦷 FLOSS Funding

While galtzo-floss tools are free software and will always be, the project would benefit immensely from some funding. Raising a monthly budget of... "dollars" would make the project more sustainable.

We welcome both individual and corporate sponsors! We also offer a wide array of funding channels to account for your preferences. Currently, Open Collective is our preferred funding platform.

If you're working in a company that's making significant use of galtzo-floss tools we'd appreciate it if you suggest to your company to become a galtzo-floss sponsor.

You can support the development of galtzo-floss tools via GitHub Sponsors, Liberapay, PayPal, Open Collective and Tidelift.

| 📍 NOTE | |----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | If doing a sponsorship in the form of donation is problematic for your company
from an accounting standpoint, we'd recommend the use of Tidelift,
where you can get a support-like subscription instead. |

Open Collective for Individuals

Support us with a monthly donation and help us continue our activities. [Become a backer]

NOTE: kettle-readme-backers updates this list every day, automatically.

No backers yet. Be the first!

Open Collective for Organizations

Become a sponsor and get your logo on our README on GitHub with a link to your site. [Become a sponsor]

NOTE: kettle-readme-backers updates this list every day, automatically.

No sponsors yet. Be the first!

Another way to support open-source

I’m driven by a passion to foster a thriving open-source community – a space where people can tackle complex problems, no matter how small. Revitalizing libraries that have fallen into disrepair, and building new libraries focused on solving real-world challenges, are my passions. I was recently affected by layoffs, and the tech jobs market is unwelcoming. I’m reaching out here because your support would significantly aid my efforts to provide for my family, and my farm (11 🐔 chickens, 2 🐶 dogs, 3 🐰 rabbits, 8 🐈‍ cats).

If you work at a company that uses my work, please encourage them to support me as a corporate sponsor. My work on gems you use might show up in bundle fund.

I’m developing a new library, floss_funding, designed to empower open-source developers like myself to get paid for the work we do, in a sustainable way. Please give it a look.

Floss-Funding.dev: 👉️ No network calls. 👉️ No tracking. 👉️ No oversight. 👉️ Minimal crypto hashing. 💡 Easily disabled nags

🔐 Security

See SECURITY.md.

🤝 Contributing

If you need some ideas of where to help, you could work on adding more code coverage, or if it is already 💯 (see below) check issues or PRs, or use the gem and think about how it could be better.

We so if you make changes, remember to update it.

See CONTRIBUTING.md for more detailed instructions.

🚀 Release Instructions

See CONTRIBUTING.md.

Code Coverage

Coverage service badges

🪇 Code of Conduct

Everyone interacting with this project's codebases, issue trackers, chat rooms and mailing lists agrees to follow the .

🌈 Contributors

Made with contributors-img.

Also see GitLab Contributors: https://gitlab.com/galtzo-floss/activesupport-tagged_logging/-/graphs/main

⭐️ Star History

📌 Versioning

This library follows for its public API where practical. For most applications, prefer the Pessimistic Version Constraint with two digits of precision.

For example:

spec.add_dependency("activesupport-tagged_logging", "~> 3.0")

📌 Is "Platform Support" part of the public API? More details inside.

Dropping support for a platform can be a breaking change for affected users. If a release changes supported platforms, it should be called out clearly in the changelog and versioned with that impact in mind.

To get a better understanding of how SemVer is intended to work over a project's lifetime, read this article from the creator of SemVer:

"Major Version Numbers are Not Sacred"

See CHANGELOG.md for a list of releases.

📄 License

The gem is available as open source under the terms of the MIT .

© Copyright

See LICENSE.md for the official copyright notice.

🤑 A request for help

Maintainers have teeth and need to pay their dentists. After getting laid off in an RIF in March, and encountering difficulty finding a new one, I began spending most of my time building open source tools. I'm hoping to be able to pay for my kids' health insurance this month, so if you value the work I am doing, I need your support. Please consider sponsoring me or the project.

To join the community or get help, use the RubyForum or Discord.

To say "thanks!" ☝️ Join the community or 👇️ send money.

💌 💌 💌

Please give the project a star ⭐ ♥.

Many parts of this project are actively managed by a kettle-jem smart template utilizing StructuredMerge.org merge contracts.

Thanks for RTFM. ☺️

Field	Value
Package	activesupport-tagged_logging
Description	💎 Rails v8 ActiveSupport::TaggedLogging, fixed & backported to Rails v5.2+ & Ruby 2.7+
Homepage	https://github.com/galtzo-floss/activesupport-tagged_logging
Source	https://github.com/galtzo-floss/activesupport-tagged_logging
License	`MIT`
Funding	https://github.com/sponsors/pboling, https://ko-fi.com/pboling, https://liberapay.com/pboling/donate, https://opencollective.com/galtzo-floss, https://thanks.dev/u/gh/pboling, https://tidelift.com/funding/github/rubygems/activesupport-tagged_logging, https://www.buymeacoffee.com/pboling