title: How to prevent log bombing using logback?
body: <p>I'm not sure the term "bombing" is the right one. By bombing, I mean a log happening many times with the same content (message and args).</p>
  
  <p>For example, a denial of service attach might cause a log warning that an unauthenticated user is trying to access some API. log:</p>
  
  <pre><code>[03-29 11:26:01.000] missing token
  [03-29 11:26:01.001] missing token
  [03-29 11:26:01.005] missing token
  ... overall 100000 times
  </code></pre>
  
  <p>The problem I'm trying to tackle is preventing the log from being very large. Size is a problem. Also, other important messages might not be seen because of the overwhelming number of the repeating message.</p>
  
  <p>I'd like to be able to prevent such a log bombing and have some aggregated message like:</p>
  
  <pre><code>[03-29 11:26:01.000] missing token
  [03-29 11:26:06.000] missing token [silenced. Overall 100000 times]
  </code></pre>
  
  <p>So, I'm looking for 2 features here:</p>
  
  <ol>
  <li>Silence too repetitive logs.</li>
  <li>Show a summery of the silenced logs.</li>
  </ol>
  
  <p><strong>Any idea if and how this can be done using logback?</strong> Perhaps another logging tool can support this? Thanks.</p>