| Type |
Key |
Summary |
By |
Status |
Resolution |
Fix Version |
| Improvement |
LOG4J2-2443 |
Consistent validation exceptions |
|
Closed |
Fixed |
Log4j-Audit 1.0.1 |
| Bug |
LOG4J2-2429 |
Setting the exceptionHandler on the AuditEvent sets it as a ThreadContext variable |
|
Closed |
Fixed |
Log4j-Audit 1.0.1 |
| Improvement |
LOG4J2-2428 |
Use the AuditExceptionHandler for validation exceptions |
|
Closed |
Fixed |
Log4j-Audit 1.0.1 |
| Bug |
LOG4J2-2421 |
AbstractEventLogger.logEvent doesn't check for missing required context attributes |
|
Closed |
Fixed |
Log4j-Audit 1.0.1 |
| Improvement |
LOG4J2-2452 |
Add verbose parameter to the Log4j audit Maven plugin |
|
Closed |
Fixed |
Log4j-Audit 1.0.1 |
| Improvement |
LOG4J2-2442 |
Normalize the event names logged through AbstractEventLogger.logEvent |
|
Closed |
Fixed |
Log4j-Audit 1.0.1 |
| Improvement |
LOG4J2-2440 |
AuditEvents should provide some basic toString() |
|
Closed |
Fixed |
Log4j-Audit 1.0.1 |
| Improvement |
LOG4J2-2420 |
RequestContextFilter logging cleanup |
|
Closed |
Fixed |
Log4j-Audit 1.0.1 |
| Bug |
LOG4J2-2417 |
Better handling of optional properties |
Ralph Goers |
Closed |
Fixed |
Log4j-Audit 1.0.1 |
| Improvement |
LOG4J2-2431 |
Narrow the type returned by LogEventFactory.getEvent |
|
Closed |
Fixed |
Log4j-Audit 1.0.1 |
