title: Best practices for using Markers in SLF4J/Logback
body: <p>We are using SLF4J+Logback combination at our project for a while now and are quite happy with it, but our logging strategy is fairly simple, using straightforward class based loggers and no fancy stuff like MDC or Markers.</p>
  
  <p>What I want to know is if anybody in the community actually uses these features and how they are used to improve logging/filtering.</p>
  
  <p>I am specially interested in where, why and how would one use<sup>[1]</sup> Markers for logging. They strike me as a pretty neat feature for adding semantic context into the logging - e.g. while a class may be handling multiple concerns, one may use task/concern specific markers to discriminate log statements.</p>
  
  <p>What may be the best practices, conventions or strategies for creating and using markers in logging.</p>
  
  <p><strong>Update:</strong> I guess, what I am really after is not so much <em>why</em> to use markers, but rather the <em>how</em> part &mdash; is there some good practices of naming markers (e.g. using plain text with spaces or dash/underscore/punctuation delimited keyword style names), should there be some sort of pool of "standard names", naming stuff based on the business functions. The questions I can probably figure out for myself, but if I want to use these features systematically and introduce them to a team of developers, it makes sense to have some formalizeable set of guidelines around...</p>
  
  <hr>
  
  <p><sup>[1]</sup> - By asking how to <em>use</em> markers I am not really asking how to use API (it is really quite straight forward) - I am rather referring to the more general level of how would one set up logging around using markers consistently</p>