[SERVER-2206] Improve default logging configuration for puppetserver Created: 2018/05/11  Updated: 2018/05/24  Resolved: 2018/05/24

Status: Closed
Project: Puppet Server
Component/s: None
Affects Version/s: None
Fix Version/s: SERVER 6.0.0

Type: New Feature Priority: Normal
Reporter: Charlie Sharpsteen Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to TK-426 Investigate apparent breakage of "sca... Closed
Template:
Team: Server
Release Notes: Not Needed
Release Notes Summary: Docs included in PR
QA Risk Assessment: Needs Assessment

 Description   

The default logback configuration bundled with the puppetserver package can be
improved by:

  • Updating the configuration to no longer require a service restart or reload
    in order for changes to be picked up (TK-426).
  • Formatting timestamps in application logs to include the time zone in order
    to enable debugging of geographically distributed installations (PE-13490).

These changes will allow DEBUG logging to be enabled without requiring a restart
or reload that may destroy application state and improve the usefulness of log
data from installations that span multiple time zones.

Recommendations:

  • Logback configuration should include scanPeriod="60 seconds" to allow
    log levels and other settings to be adjusted without requiring service
    restarts or reloads.
  • Logback patterns for application logs should use a RFC 3339
    compatible representation that includes the Time Zone. A Java
    SimpleDateFormat that works with logback is:

%d{yyyy-MM-dd'T'HH:mm:ss.SSSXXX}


Generated at Sat Dec 07 21:34:33 PST 2019 using JIRA 7.7.1#77002-sha1:e75ca93d5574d9409c0630b81c894d9065296414.