If I understand things correctly it’s suppressing info and debug in production mode by design. Blaming logster/lib/logster/rails/railtie.rb at main · discourse/logster · GitHub
store.level = Logger::Severity::WARN if Rails.env.production?
From a blog post
In production mode it aggregates similar errors by fingerprinting backtraces listening for warnings/errors and fatal messages. The intention is to display a list of open application problems that can somehow be resolved.
In development mode it provides a full fire-hose of all logs produced by Rails. (debug and up). This has significant advantages over console as you have proper access to backtraces for every log line.