# Production 환경에서 /logs에 Info 레벨 로그 표시

**URL:** https://meta.discourse.org/t/show-info-level-logs-in-production-in-logs/312447
**Category:** Feature
**Created:** [6월 17, 2024, 8:19오후 UTC](https://meta.discourse.org/t/show-info-level-logs-in-production-in-logs/312447 "2024-06-17T20:19:44Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![37Rb](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/37rb/32/224158_2.png) [@37Rb](https://meta.discourse.org/u/37Rb)
#### Post date: [6월 18, 2024, 5:36오후 UTC](https://meta.discourse.org/t/show-info-level-logs-in-production-in-logs/312447/2 "2024-06-18T17:36:11Z")

</div>

이는 의도된 동작이라는 점이 지적되었습니다.

> [@프로덕션 환경에서 로그 레벨을 변경해도 되나요?](https://meta.discourse.org/t/alter-log-level-in-production/238375/5?u=37rb):
>
> 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 mo…

그러나 info 레벨 메시지는 의도적으로 [Logster Redis에서 제외](https://github.com/discourse/logster/blame/main/lib/logster/rails/railtie.rb#L16)되고, 로그 파일 자체에는 [포함](https://github.com/discourse/discourse/blob/main/config/environments/production.rb#L25)되도록 설계된 것으로 보입니다.

info 레벨 메시지는 프로덕션 환경에서 유용할 수 있습니다. 저희 사용 사례에서는 특히 매우 유용할 것입니다. info 레벨 메시지를 원하는 관리자는 로그 파일에서 직접 가져오도록 의도된 것인가요?

---

_[View the full topic](https://meta.discourse.org/t/show-info-level-logs-in-production-in-logs/312447)._