This ticket represents an investigation task for issues listed in task #673. The object of this task is to scope out what can be done as "phase 1" so that the TPS re-write work as well as new code might be able to conform to. The result of this task is the following: 1. a guideline for how messages are to be logged (formats, levels, etc.); publish the guideline so that cs developers can follow, and qe can verify. 2. a thorough understanding (and document the understanding) of what kind of "levelling" our current JAVA logging system provides, so that we know if it is actually sufficient for what we need (but has just been mis-used?) or is there is indeed a defect that we need to fix. what's the defect(s) if any.
proposed Milestone: 10.2.1 - Per Dogtag 10.2.3 meeting of 09/25/2014
Reminder: This ticket is only for the investigation portion; PKI TRAC Ticket #673 - Better (for debugging) log messages or logging system is for the actual task itself, and is currently assigned to the Dogtag 10.3 milestone.
Write up on the current dogtag logging system and futures requirements -
http://pki.fedoraproject.org/wiki/Logging_mechanism_in_Dogtag
After discussion with edewata on 12/11/2014, it was determined that this ticket could be re-assigned to him and moved to 10.3.
Metadata Update from @cfu: - Issue assigned to edewata - Issue set to the milestone: UNTRIAGED
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/1252
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.
Metadata Update from @dmoluguw: - Issue close_status updated to: migrated - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.