-
Bug
-
Resolution: Done
-
Blocker
-
7.1.0.DR17
-
None
The format of rotating-file-audit-log's timestamp is insufficient. It lacks the information about seconds which might be a problem in an environment with thousands of active users.
Furthermore the format of timestamp is inconsistent with the file-audit-log.
file-audit-log:
2017-05-03 13:44:07
rotating-file-audit-log:
5/3/17 1:44 PM
Suggestions for improvement:
Use the same format of timestamp in_rotating-file-audit-log_ as is already used in file-audit-log.
- is cloned by
-
WFCORE-2755 Elytron Audit Logging: rotating-file-audit-log's event timestamp lacks information about seconds
- Resolved
- is incorporated by
-
JBEAP-10508 (7.1.0) Upgrade to WildFly Core to 3.0.0.Beta21
- Closed
- is related to
-
JBEAP-9019 Elytron Audit Logging's event timestamp lacks information about seconds
- Closed