Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-49805

Prototype error telemetry logging with a Java Util Logger configuration

    • Icon: Task Task
    • Resolution: Fixed
    • Icon: Minor Minor
    • evergreen
    • None
    • Evergreen - Milestone 1

      Per this discussion on jenkinsci-dev, we should prototype whether we can inject custom logger simply through the java.util.logging support already present in the JVM.

      The original thread I posted contains some requirements.

      I currently define "error telemetry" to include:

      • Uncaught exceptions which cause the Evil Jenkins 500 page
      • Logged ERROR messages, with or without exceptions
      • Logged WARN messages, with or without exceptions

      The big question I have in my mind is: can we inject some custom Java code (perhaps this has to be delivered via a plugin?) for reporting exceptions to the Evergreen services layer.

          [JENKINS-49805] Prototype error telemetry logging with a Java Util Logger configuration

          R. Tyler Croy created issue -
          R. Tyler Croy made changes -
          Rank New: Ranked higher
          R. Tyler Croy made changes -
          Sprint New: Essentials - Milestone 1 [ 511 ]
          R. Tyler Croy made changes -
          Epic Link New: JENKINS-49844 [ 188828 ]
          Baptiste Mathus made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]
          Baptiste Mathus made changes -
          Description Original: Per [this discussion on jenkinsci-dev|https://groups.google.com/d/msg/jenkinsci-dev/1qtL_ADxfFE/69W2DovKAAAJ], we should prototype whether we can inject custom logger simply through the {{java.util.logging}} support already present in the JVM.

          The [original thread|https://groups.google.com/d/msg/jenkinsci-dev/1qtL_ADxfFE/W2_1UOzJAAAJ] I posted contains some requirements.

          The big question I have in my mind is: can we inject some custom Java code (perhaps this has to be delivered via [a plugin|https://github.com/jenkinsci/sentry-plugin]?) for reporting exceptions to the Evergreen services layer.
          New: Per [this discussion on jenkinsci-dev|https://groups.google.com/d/msg/jenkinsci-dev/1qtL_ADxfFE/69W2DovKAAAJ], we should prototype whether we can inject custom logger simply through the {{java.util.logging}} support already present in the JVM.

          The [original thread|https://groups.google.com/d/msg/jenkinsci-dev/1qtL_ADxfFE/W2_1UOzJAAAJ] I posted contains some requirements.

          I currently define "error telemetry" to include:

           * Uncaught exceptions which cause the Evil Jenkins 500 page
           * Logged ERROR messages, with or without exceptions
           * Logged WARN messages, with or without exceptions

          The big question I have in my mind is: can we inject some custom Java code (perhaps this has to be delivered via [a plugin|https://github.com/jenkinsci/sentry-plugin]?) for reporting exceptions to the Evergreen services layer.
          Baptiste Mathus made changes -
          Link New: This issue relates to JENKINS-50294 [ JENKINS-50294 ]
          Baptiste Mathus made changes -
          Status Original: In Progress [ 3 ] New: In Review [ 10005 ]
          Baptiste Mathus made changes -
          Status Original: In Review [ 10005 ] New: In Progress [ 3 ]
          Baptiste Mathus made changes -
          Remote Link New: This issue links to "JEP-304: Essentials Client Error Telemetry Logging (Web Link)" [ 20384 ]
          Baptiste Mathus made changes -
          Link New: This issue relates to HOSTING-541 [ HOSTING-541 ]

            batmat Baptiste Mathus
            rtyler R. Tyler Croy
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: