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

Java exception should be reported to Sentry using captureMessage too

    XMLWordPrintable

    Details

    • Similar Issues:
    • Sprint:
      Evergreen - Milestone 2

      Description

      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.

        Attachments

        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

          Activity

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

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

           !example.png|thumbnail!
          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}}.
          rtyler R. Tyler Croy made changes -
          Sprint Evergreen - Milestone 2 [ 516 ]
          rtyler R. Tyler Croy made changes -
          Rank Ranked higher
          rtyler R. Tyler Croy made changes -
          Sprint Evergreen - Milestone 2 [ 516 ]
          Assignee R. Tyler Croy [ rtyler ] Mandie Smith [ asmith_cb ]
          rtyler R. Tyler Croy made changes -
          Rank Ranked higher
          asmith_cb Mandie Smith made changes -
          Assignee Mandie Smith [ asmith_cb ]
          bssmasta Billy Bunns made changes -
          Rank Ranked higher
          bssmasta Billy Bunns made changes -
          Rank Ranked lower

            People

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

              Dates

              Created:
              Updated: