The current logging service was custom coded for this project some time ago. There are now other logging services (e.g. java.util.logging, Log4j) that provide more functionality, are simpler to use, well developed and tested, thread-safe, high performance, etc. We should consider the possibility of replacing the current logging service.
This is needed to simplify unit testing by reducing dependencies on custom logging service.
This will fix ticket #814 as well.
attachment pki-edewata-0834-1-Updated-PKI-server-logging-service-to-use-JUL.patch
attachment pki-edewata-0839-Updated-PKI-server-logging-service-to-use-SLF4J.patch
attachment pki-edewata-0840-Added-upgrade-scripts-for-PKI-server-logging-service.patch
With the new logging framework, high level error/warning messages can be logged in multiple locations at once, e.g. debug log, selftest log, and console/journal. This way the admin only needs to look at one place (i.e. console/journal) to see if there's a problem on the server. The debug log is only needed to actually troubleshoot the problem and it can be disabled to improve performance and reduce storage requirement.
Changes in master:
In ticket #673 cfu wrote:
Our current logging system needs improvement for a couple reasons:
When things fail, it's hard to pinpoint the exact location of failure. Very often the errors bubble up (e.g. JAVA exceptions) and by the time it is noticed, it's hard to tell exactly where the failure occurs. We need some way to make it so that the exact errors can be easily identified (e.g. reserve some unique string such as "ALERT")
The logging system is supposed to be layered with one layer encompassing all messages from another layer. However, at some point, we have lost that layered design and many messages would occur in system or error logs but not in the debug log.
basic misconfiguration issues are not spotted right from the start (system down, etc.)
Metadata Update from @edewata: - Issue assigned to edewata - Issue set to the milestone: 10.4
The RollingLogFile should be replaced with the new logging framework as well. This will affect audit, transaction, and system logs.
Metadata Update from @edewata: - Custom field feature adjusted to '' - Custom field proposedmilestone adjusted to '' - Custom field proposedpriority adjusted to '' - Custom field reviewer adjusted to '' - Custom field version adjusted to '' - Issue close_status updated to: None
Metadata Update from @edewata: - Issue set to the milestone: FUTURE (was: 10.4)
Metadata Update from @edewata: - Issue set to the milestone: 10.6 (was: FUTURE)
Fixed in master branch:
Metadata Update from @edewata: - Issue close_status updated to: fixed - Issue set to the milestone: 10.6.0 (was: 10.6) - Issue status updated to: Closed (was: Open)
Metadata Update from @mharmsen: - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1596900
Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.
This issue has been cloned to GitHub and is available here: https://github.com/dogtagpki/pki/issues/766
If you want to receive further updates on the issue, please navigate to the GitHub issue and click on Subscribe button.
Subscribe
Thank you for understanding, and we apologize for any inconvenience.
Login to comment on this ticket.