# Wrapper log file headers

**URL:** <https://forum.inductiveautomation.com/t/wrapper-log-file-headers/57232>\
**Category:** Ignition\
**Created:** [March 15, 2022, 8:36pm UTC](https://forum.inductiveautomation.com/t/wrapper-log-file-headers/57232 "2022-03-15T20:36:05Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**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:** [March 15, 2022, 10:04pm UTC](https://forum.inductiveautomation.com/t/wrapper-log-file-headers/57232/4 "2022-03-15T22:04:32Z")

</div>

Logback (via the logback.xml file) gives you programmatic access to standard logging output (which _is_ distinct from `stdout` of the process, but generally all you need for debugging).  
There’s some discussion in [this thread](https://forum.inductiveautomation.com/t/configure-wrapper-log-for-single-line-messages/46198) about using that output more directly in other tools.

---

_[View the full topic](https://forum.inductiveautomation.com/t/wrapper-log-file-headers/57232)._