37Rb
June 18, 2024, 5:36pm
2
It was pointed out that this is by design.
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 mo…
However, it appears info level messages are only excluded from Logster Redis by design and are intentionally included in the log file itself .
Info level messages can be useful in production. For our use case, they would be very useful. Is the intention that admins who want info level messages should get them directly from the log file?