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

      Regardless of whether we use a third party service, like Sentry, for error telemetry, it's still very important that we receive Jenkins error telemetry at an endpoint we control.

      This will provide us benefits down the road of choosing another service provider, or side-channeling the telemetry into our own analytics database.

      This API contract I would expect to be defined in a JEP, and then we'll create a corresponding IEP when the service is implemented and ready for deployment

          [JENKINS-49811] Prototype Evergreen Error service API

          R. Tyler Croy created issue -
          R. Tyler Croy made changes -
          Rank New: Ranked higher
          R. Tyler Croy made changes -
          Rank New: Ranked lower
          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 -
          Rank New: Ranked higher
          Baptiste Mathus made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]
          Baptiste Mathus made changes -
          Link New: This issue relates to JENKINS-49805 [ JENKINS-49805 ]
          Baptiste Mathus made changes -
          Summary Original: Define Evergreen Error service API New: Prototype Evergreen Error service API
          Baptiste Mathus made changes -
          Remote Link New: This issue links to "PR (Web Link)" [ 20625 ]
          Baptiste Mathus made changes -
          Link New: This issue blocks JENKINS-51140 [ JENKINS-51140 ]

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

              Created:
              Updated:
              Resolved: