Log Levels are a common issue, especially when doing diagnostics on a system, support tickets. Often a first diagnostic step is Log Level is set to ERROR or Level 9, which outputs large amounts of data, increases overhead for a machine, process, even disk space. When a diagnostic or support ticket is complete, I've never seen cleanup work requested/reminded to make sure to set log levels back to normal levels. As such, you eventually reach a point where most services may be running multiple items at a higher level eventually causing other issues, or degradation.

As a preventative/monitoring measure, I'd suggest putting a "log monitor" line in the TL Status report. If any log levels are set to their respective highest level, it be run as a WARN alert line in the top of the TLStatus emailed report. This constant pestering in email will be a reminder to the administrator that they need to eventually reduce the log level to silence the warn, and restore the system to reduced load.

Even better might be to eventually port these to DB controlled, or at least inventoried, so a central system can show what your log levels are across the entire system. Refer to Idea: TLONPREM (https://watsonmarketing.ideas.aha.io/ideas?project=TLONPREM) -I-123