Uploaded image for project: 'Trapperkeeper'
  1. Trapperkeeper
  2. TK-426

Investigate apparent breakage of "scan" for logback configuration

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: SERVER 6.0.0
    • Component/s: None
    • Template:
    • Story Points:
      5
    • CS Priority:
      Normal
    • CS Frequency:
      4 - 50-90% of Customers
    • CS Severity:
      2 - Annoyance
    • CS Business Value:
      4 - $$$$$
    • CS Impact:
      Support interactions would be much smoother if we just set this to scan every 60 seconds. It would remove the need to ask customers to restart puppetserver during troubleshooting which can be lengthy at many customers.
    • QA Risk Assessment:
      Needs Assessment

      Description

      In the logback.xml configuration files for various projects, we've been setting the "scan" attribute to "true" in hopes of having logback automatically notice / reload configuration file changes on the fly. We had observed that it was working for Trapperkeeper-based applications at one point in time but it no longer appears to be working, most recently tested with logback-classic version 1.1.7. We should investigate this further to see if there's something we need to change in Trapperkeeper to continue supporting the feature and/or if there's a bug in logback itself.

        Attachments

          Issue Links

          relates to

          New Feature - A new feature of the product, which has yet to be developed. SERVER-2206 Improve default logging configuration for puppetserver

          • Normal - Regular issue, some loss of functionality under specific circumstances.
          • Closed

          Improvement - An improvement or enhancement to an existing feature or task. TK-424 Reinitialize logback during reload

          • Normal - Regular issue, some loss of functionality under specific circumstances.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. DOCUMENT-642 Docs on logging say I don't need to restart to pick up change. But I do...

          • Normal - Regular issue, some loss of functionality under specific circumstances.
          • Closed

          Improvement - An improvement or enhancement to an existing feature or task. PDB-3884 Improve default logging configuration for PuppetDB

          • Major - Major loss of function.
          • Closed
          links to

          Web Link LOGBACK-1194

          Web Link PE Premium : https://puppetlabs.zendesk.com/agent/tickets/24153

            Activity

              People

              Assignee:
              chuck Charlie Sharpsteen
              Reporter:
              jeremy.barlow Jeremy Barlow
              Votes:
              0 Vote for this issue
              Watchers:
              10 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Zendesk Support