# Alter log level in Production?

**URL:** https://meta.discourse.org/t/alter-log-level-in-production/238375
**Category:** Self-hosting
**Created:** [September 7, 2022, 8:28pm UTC](https://meta.discourse.org/t/alter-log-level-in-production/238375 "2022-09-07T20:28:31Z")
**Posts on this page:** 1
**Showing post:** 5

<div class="post-metadata">

### Author: ![RGJ](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/rgj/32/523185_2.png) [@RGJ](https://meta.discourse.org/u/RGJ)
#### Post date: [June 17, 2024, 10:13pm UTC](https://meta.discourse.org/t/alter-log-level-in-production/238375/5 "2024-06-17T22:13:40Z")

</div>

> [@merefield](#):
>
> So I’m still at a loss why the info level logs are not showing in `/logs`

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](https://github.com/discourse/logster/blame/main/lib/logster/rails/railtie.rb#L16)

`store.level = Logger::Severity::WARN if Rails.env.production?`

From [a blog post](https://samsaffron.com/archive/2018/12/27/logster-and-our-logging-strategy-at-discourse)

> 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.

---

_[View the full topic](https://meta.discourse.org/t/alter-log-level-in-production/238375)._