Description
Log4j provides the option to specify marker for each individual log entry. The behaviour of these Markers can be specified in log4j config file. There is a lot what log4j can do to marked entries: hide from all and-or selected loggers, forward, encrypt, reformat etc.
Since the log4j config file is located in odlparent/karaf/opendaylight-karaf-resources/src/main/resources/etc/org.ops4j.pax.logging.cfg it is only logical to create odlparent artifact which will provide the Markers to all child ODL projects so the marking is consistent.
Attachments
Issue Links
- blocks
-
NETCONF-643 NetconfMessageToXmlEncoder can leak sensitive data
-
- Resolved
-
- mentioned in
-
Page Loading...
| # | Subject | Branch | Project | Status | CR | V |
|---|---|---|---|---|---|---|
| 88536,7 | Add logging-markers artifact for marking sensitive logs | master | odlparent | Status: MERGED | +2 | +1 |
| 89698,2 | Add logging-markers artifact for marking sensitive logs | 5.0.x | odlparent | Status: MERGED | +2 | +1 |
| 89741,2 | Integrate logging-markers | 5.0.x | odlparent | Status: MERGED | +2 | +1 |
| 89742,1 | Integrate logging-markers | master | odlparent | Status: MERGED | +2 | +1 |
| 89775,1 | Add logging-markers artifact for marking sensitive logs | 6.0.x | odlparent | Status: MERGED | +2 | +1 |
| 89776,1 | Integrate logging-markers | 6.0.x | odlparent | Status: MERGED | +2 | +1 |
| 90120,1 | Add logging-markers to javadocs | master | odlparent | Status: MERGED | +2 | +1 |
| 90123,1 | Add logging-markers to javadocs | 6.0.x | odlparent | Status: MERGED | +2 | +1 |