What do you do when need "trace" level logging in a Confluence add-on?

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 says:

TRACE - n/a within confluence

So, what do you do in case you want to use trace()?

1 Like

Trying to do the same thing and came across this - 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

1 Like