# Mostrar logs de nível Info em Produção em /logs

**URL:** https://meta.discourse.org/t/show-info-level-logs-in-production-in-logs/312447
**Category:** Feature
**Created:** [17 Junho , 2024 20: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:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![merefield](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/merefield/32/176214_2.png) [@merefield](https://meta.discourse.org/u/merefield)
#### Post date: [17 Junho , 2024 20:19 UTC](https://meta.discourse.org/t/show-info-level-logs-in-production-in-logs/312447/1 "2024-06-17T20:19:44Z")

</div>

Atualmente, não parece possível visualizar logs de nível Info na interface `/logs`.

Os dados podem estar no arquivo `production.log`, mas não é possível visualizá-los na interface, apesar das caixas de seleção!

![image](https://global.discourse-cdn.com/meta/original/4X/e/4/3/e43a9c0cbcf0b12e17669737ad5da5259a6b7941.png)

Forneça uma opção para permitir isso.

Na era dos LLMs, logs de nível info são ainda mais importantes e úteis!

Veja:

> [@Alter log level in Production?](https://meta.discourse.org/t/alter-log-level-in-production/238375/4?u=merefield):
>
> 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…](https://github.com/search?q=repo%3Adiscourse%2Fdiscourse%20Logger%3A%3AWARN&type=code)

---

<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: [18 Junho , 2024 17:36 UTC](https://meta.discourse.org/t/show-info-level-logs-in-production-in-logs/312447/2 "2024-06-18T17:36:11Z")

</div>

Foi apontado que isso é intencional.

> [@Alter log level in Production?](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…

No entanto, parece que as mensagens de nível `info` são apenas [excluídas do Logster Redis](https://github.com/discourse/logster/blame/main/lib/logster/rails/railtie.rb#L16) por design e são intencionalmente [incluídas no próprio arquivo de log](https://github.com/discourse/discourse/blob/main/config/environments/production.rb#L25).

Mensagens de nível `info` podem ser úteis em produção. Para o nosso caso de uso, elas seriam muito úteis. A intenção é que os administradores que desejam mensagens de nível `info` as recebam diretamente do arquivo de log?
