# Wrapper Log/ Log Level INFO **URL:** \ **Category:** Ignition\ **Created:** [November 25, 2025, 5:40pm UTC](https://forum.inductiveautomation.com/t/wrapper-log-log-level-info/112428 "2025-11-25T17:40:25Z")\ **Posts on this page:** 1\ **Showing post:** 15
**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\ **Post date:** [November 25, 2025, 10:52pm UTC](https://forum.inductiveautomation.com/t/wrapper-log-log-level-info/112428/15 "2025-11-25T22:52:08Z")
I would skip the wrapper.log entirely. Configure logback to write to a separate file entirely in whatever format you choose. This post has some possible inspiration: > [@Ignition Observability](https://forum.inductiveautomation.com/t/ignition-observability/110650): > > Overview Introduction / Motivation Ignition doesn’t run in a vacuum—it sits at the center of controllers, networks, databases, brokers, and other infrastructure and applications that all depend on each other. In IT operations, the way to keep that whole picture healthy is observability: a single place to see correlated traces, metrics, and logs across every layer so you can spot causes and effects quickly. At [4IR](https://www.4ir.cloud), we already monitor the rest of our ecosystem this way, but Ignition was the missin… --- _[View the full topic](https://forum.inductiveautomation.com/t/wrapper-log-log-level-info/112428)._