Hi all,<br><br>Our application makes an intensive use of Profiler (<a href="http://www.slf4j.org/extensions.html#profiler">http://www.slf4j.org/extensions.html#profiler</a>).<br>It has been very useful during the development stage an we would like to keep it at production stage but there is a problem since its &quot;log level&quot; is hard-coded to &quot;debug&quot;.<br>

<br>Currently the profiler use the same application class logger so if log level is set to &quot;info&quot; in our production environment we lose the &quot;profiler&quot; log :-(<br><br>Alternatives:<br><ul><li>Use different loggers for application and profiler &gt;--&gt;&gt; It requires to refactoring all the code and remember that any new Profiler that will be used need to set a custom logger instead of the default class logger.<br>

<br></li><li>Open a request to modify Profiler in order to set a custom log level.<br><br></li><li>Keep minimum log level to &quot;debug&quot; and make use of a Filter to accept any log event with marker=PROFILER, otherwise only accept if log level &gt;= INFO &gt;--&gt;&gt; It only will work with LogBack but Profiler belongs to SLF4J so it should work with any bridge.</li>

</ul><p>Any other way?</p><p>BR,<br>/César.<br></p>