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

Java exception should be reported to Sentry using captureMessage too

XMLWordPrintable

    • Evergreen - Milestone 2

      Java exceptions are reported in an unclear way in Sentry UI

      For messages, it's more directly readable:

      captureException actually always captures the same stack trace and points us in the UI to our Sentry.sendOutput central code, which is not what we want:

      Expected behavior

      Exception message should be used as the title. Probably we simply need to process Java exceptions the same way we do for other logs and just use captureMessage.

        1. example.png
          example.png
          31 kB
        2. node stack captured.png
          node stack captured.png
          60 kB
        3. screenshot-1.png
          screenshot-1.png
          20 kB

          [JENKINS-53552] Java exception should be reported to Sentry using captureMessage too

          Baptiste Mathus created issue -
          Baptiste Mathus made changes -
          Attachment New: example.png [ 44472 ]
          Baptiste Mathus made changes -
          Description New: h3. Java exceptions are reported in an unclear way in Sentry UI

           !example.png|thumbnail!
          Baptiste Mathus made changes -
          Attachment New: screenshot-1.png [ 44473 ]
          Baptiste Mathus made changes -
          Attachment New: node stack captured.png [ 44474 ]
          Baptiste Mathus made changes -
          Description Original: h3. Java exceptions are reported in an unclear way in Sentry UI

           !example.png|thumbnail!           		New: h3. Java exceptions are reported in an unclear way in Sentry UI

           !example.png!

          For messages, it's more directly readable:
           !screenshot-1.png!

          {{captureException}} actually always captures the same stack trace and points us in the UI to our Sentry.sendOutput central code, which is not what we want:

           !node stack captured.png!

          h3. Expected behavior

          Exception message should be used as the title. Probably we simply need to process Java exceptions the same way we do for other logs and just use {{captureMessage}}.
          R. Tyler Croy made changes -
          Sprint Original: Evergreen - Milestone 2 [ 516 ]
          R. Tyler Croy made changes -
          Rank New: Ranked higher
          R. Tyler Croy made changes -
          Sprint New: Evergreen - Milestone 2 [ 516 ]
          Assignee Original: R. Tyler Croy [ rtyler ] New: Mandie Smith [ asmith_cb ]
          R. Tyler Croy made changes -
          Rank New: Ranked higher

            Unassigned Unassigned
            batmat Baptiste Mathus
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: