title: Logback: Prevent appender inheritance? Or: find non-routed logger?
body: <p>I'm completely new to Logback and I can't really find an answer to a basic conceptual question:</p>
  
  <p>What I'm trying to accomplish is either:</p>
  
  <ul>
  <li>Prevent appender inheritance, i.e., prevent a certain logger to use the root logger for instance. Kind of like a veto to use a certain appender.</li>
  <li>Generate a kind of "fall back" logger, which will be used if (and <em>only</em> if) no logger element matches the basic selection rule.</li>
  </ul>
  
  <p>The motivation for this is that in my use case I do not want a huge global log file. Instead I have split logging into small units / log files. My problem is: I sometimes make mistakes in my logger-split-logic with the result that some messages do not show up in my logs (e.g., a logger obtained from <code>LoggerFactory.getLogger("non-existent-logger")</code>). I can obviously set up an appender for the root logger but since this appender is inherited to all loggers the resulting log file will be huge and it is difficult to track down loggers which have not been routed according to my split rules. So my question is how to deal with this problem in Logback?</p>