Currently it doesn’t seem possible to view Info level logs in the /logs interface.
The data can be in the production.log file, but it is not possible to view it in the interface despite the check boxes!
Provide an option to allow this.
In the era of LLMs, info level logs are even more important and useful!
See:
More things I’ve tried:
I’ve checked production.log and the info logs I want are there!
I’ve looked at the output of Logster.config on rails console and it’s not obviously useful.
ditto /vendor/bundle/ruby/3.2.0/gems/logster-2.19.1/lib/logster/configuration.rb
So I’m still at a loss why the info level logs are not showing in /logs
Clearly something is filtering out the info level logs between production.log and Logster.
https://github.com/search?q=repo%3Adiscourse%2Fdiscourse%20Logger%3A%3A…
3 Likes
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?
