<h3 class="anchored">What if I need more configurations?</h3>

<p>Logback gives you some additional options for passing in the configurations. Let's say we have a single Jar that has many main methods inside of it. Maybe one or more services and potentially some mains that are run as cron jobs. In this case <code>src/main/resources/logback.xml</code> works for our services but we want a different config file for the cron jobs. Simply make a <code>src/main/resources/cron-logback.xml</code> and when you start the java process add the system property flag <nobr><code>-Dlogback.configurationFile=logback-crons.xml</code></nobr>. This will force logback to use that specific file instead of the default.</p>

<pre class="line-numbers"><code class="language-bash">2017-02-05 12:05:06.488 [main] INFO c.s.examples.logback.LogbackExamples - INFO

2017-02-05 12:05:06.492 [main] DEBUG c.s.examples.logback.LogbackExamples - DEBUG

2017-02-05 12:05:06.492 [main] ERROR c.s.secrets.MySecretPasswordClass - ERROR</code></pre>

<p>Notice how neither logger logged at Trace level and MySecretPasswordClass only traced Warn and above.</p>

<h3 class="anchored">Monitoring</h3>

<p>Often times even with proper logging your application can be spewing errors / exceptions in production and no one will notice for extended periods of time. Utilizing <a href="/posts/monitoring-your-jvm-with-dropwizard-metrics#logging-level-hit-counts">Dropwizard Metrics SLF4J Instrumented Appender</a> you can easiy set up graphs or alerts on warn / error rates.