# 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:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![cgele](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/cgele/32/3453_2.png) [@cgele](https://forum.inductiveautomation.com/u/cgele)\
**Post date:** [March 15, 2022, 8:36pm UTC](https://forum.inductiveautomation.com/t/wrapper-log-file-headers/57232/1 "2022-03-15T20:36:05Z")

</div>

Does anyone know the column header names in the wrapper logs?

Based on what I am seeing  
column 1 appears to be the logger type (not sure about this one)  
column 2 appears to be the java machine name  
column 3 is the date time stamp  
column 4 is the log message

I’m putting together a short presentation of system type data that Ignition offers for some IT people interested in monitoring the gateway server and I know they will have questions on this.

Thanks,  
Chris

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [March 15, 2022, 8:45pm UTC](https://forum.inductiveautomation.com/t/wrapper-log-file-headers/57232/2 "2022-03-15T20:45:13Z")

</div>

[https://wrapper.tanukisoftware.com/doc/english/prop-logfile-format.html](https://wrapper.tanukisoftware.com/doc/english/prop-logfile-format.html)

looks like format ‘LPTM’ is used by default, so:

- ‘L’ for [log level](https://wrapper.tanukisoftware.com/doc/english/prop-logfile-loglevel.html),
- ‘P’ for prefix,
- ‘T’ for time,
- ‘M’ for message.

“Prefix” does not appear to be well defined though. I think it’s trying to indicate whether it’s the wrapper itself or a JVM instance responsible for that line.

---

<div class="post-metadata">

**Author:** ![cgele](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/cgele/32/3453_2.png) [@cgele](https://forum.inductiveautomation.com/u/cgele)\
**Post date:** [March 15, 2022, 8:46pm UTC](https://forum.inductiveautomation.com/t/wrapper-log-file-headers/57232/3 "2022-03-15T20:46:09Z")

</div>

Thank you.

---

<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.

---

<div class="post-metadata">

**Author:** ![joshua.rowlison](https://avatars.discourse-cdn.com/v4/letter/j/258eb7/32.png) [@joshua.rowlison](https://forum.inductiveautomation.com/u/joshua.rowlison)\
**Post date:** [March 16, 2022, 12:15pm UTC](https://forum.inductiveautomation.com/t/wrapper-log-file-headers/57232/5 "2022-03-16T12:15:21Z")

</div>

Based on where I managed to get before having to move on, we switched our logfile-format to PM because the level and prefix entries were not particularly useful.

As I recall the level was inconsistent with the log contents, Info level attached to exceptions or something like that. We just dropped it.