Databases
StackOverflow2013
Postsdbo
POBest practices for using Markers in SLF4J/Logback
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POBest practices for using Markers in SLF4J/Logback
    primarykey
    data
    text
    <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>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USRoland Tepp
    1. USRoland Tepp
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    3. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POBest practices for using Markers in SLF4J/Logback
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POBest practices for using Markers in SLF4J/Logback
      1. USAravind R. Yarram
      1. VTFavorite
    3. VO
      singulars
      1. POBest practices for using Markers in SLF4J/Logback
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload