Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
ServiceControl default log level (Warn) makes is difficult to investigate problems #1486
The default log level for a new instance of ServiceControl is WARN. This is often insufficient to diagnose issues when customers send us log files.
It only helps when we've previously considered what could go wrong and have thought to log at the WARN level. Without any of the context of what else was happening in ServiceControl at that time, we often have to ask the customer to update their logging level (requires messing with a config file) and then restart their instance and hope that the problem occurs again.
From memory, this was dropped down to WARN when we were concerned about Raven Perf and IO.
A long running (24 hour) test with each transport to show how verbose the logs are is a good idea. If it's too verbose then we should look at making better rules around what is logged at each level to try and improve the situation.
I am wondering if we should have a timed job that runs every hour or so that causes components to log vital stats at the INFO level. Something like: