# What do you do when need "trace" level logging in a Confluence add-on? **URL:** \ **Category:** Confluence Development\ **Tags:** logging, confluence-server\ **Created:** [September 18, 2017, 11:51am UTC](https://community.developer.atlassian.com/t/what-do-you-do-when-need-trace-level-logging-in-a-confluence-add-on/8858 "2017-09-18T11:51:41Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![aron.gombas](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/aron.gombas/32/54498_2.png) [@aron.gombas](https://community.developer.atlassian.com/u/aron.gombas)\ **Post date:** [September 18, 2017, 11:51am UTC](https://community.developer.atlassian.com/t/what-do-you-do-when-need-trace-level-logging-in-a-confluence-add-on/8858/1 "2017-09-18T11:51:41Z")
One of our add-ons is using the standard log4j .trace() logging in situations that write very low-level details (lower than something that you would consider debug()). Some weeks ago we noticed that trace lines simply does **not** appear in the log. (I’m quite sure it was working previously.) And it seems even the [official documentation](https://confluence.atlassian.com/doc/log4j-logging-levels-111771719.html) says: > TRACE - n/a within confluence So, what do you do in case you want to use trace()? ---
**Author:** ![StephenMontgomery](https://avatars.discourse-cdn.com/v4/letter/s/58956e/32.png) [@StephenMontgomery](https://community.developer.atlassian.com/u/StephenMontgomery)\ **Post date:** [December 17, 2019, 4:23pm UTC](https://community.developer.atlassian.com/t/what-do-you-do-when-need-trace-level-logging-in-a-confluence-add-on/8858/2 "2019-12-17T16:23:06Z")
Trying to do the same thing and came across this - [Troubleshooting - Better Content Archiving for Confluence | Midori](https://www.midori-global.com/products/better-content-archiving-for-confluence/server/troubleshooting). Obviously still expects you to be able to have admin access to the installation to change the log4j.properties