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

Prototype Evergreen Error service API


    • 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

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