Prototype Evergreen Error service API

XMLWordPrintable

    • Type: Task
    • Resolution: Fixed
    • Priority: Minor
    • Component/s: evergreen
    • None

      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

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

              Created:
              Updated:
              Resolved: