Skip to main content
Solved

Logging level "silly" takes my infrastructure down

  • September 18, 2025
  • 2 replies
  • 67 views

Angelo Michele Pizzi

Hi everyone,

Does any of you ever tried to use the Logging level  known as silly? I’ve tried to use it for troubleshooting an issues on my env, but after less than 10 minutes, my three worker nodes were experiencing memory issues. One of my nodes went completely down, the other two remained with less than 1 GB of RAM (starting from 9 GB of free space in the beginning). I just want to know your experience/opinion on this, is it possible that my memory was not enough?

 

Best answer by kprior

It’s my understanding that this is kind of expected. Silly logging is meant for short bursts of troubleshooting and debugging. It can overwhelm the system pretty quickly otherwise (mentioned here: https://docs.cribl.io/stream/monitoring/) . Did the debug logs not offer enough information for troubleshooting what your issue was or were you just testing? 

2 replies

kprior
  • Employee
  • Answer
  • September 19, 2025

It’s my understanding that this is kind of expected. Silly logging is meant for short bursts of troubleshooting and debugging. It can overwhelm the system pretty quickly otherwise (mentioned here: https://docs.cribl.io/stream/monitoring/) . Did the debug logs not offer enough information for troubleshooting what your issue was or were you just testing? 


Angelo Michele Pizzi

It’s my understanding that this is kind of expected. Silly logging is meant for short bursts of troubleshooting and debugging. It can overwhelm the system pretty quickly otherwise (mentioned here: https://docs.cribl.io/stream/monitoring/) . Did the debug logs not offer enough information for troubleshooting what your issue was or were you just testing? 

Thanks for the reply. It was done for troubleshooting, since the debug logs didn’t offer a lot of more info than the info level. I didn’t checl the page you paste, I was missing it, that’s clear.