-
Task
-
Resolution: Fixed
-
Minor
-
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
- blocks
-
JENKINS-51140 Design (JEP) what the Error Telemetry API will be
-
- Resolved
-
- relates to
-
JENKINS-49805 Prototype error telemetry logging with a Java Util Logger configuration
-
- Closed
-
- links to
Based on the discussion we had today batmat, I wonder if it wouldn't be a better idea for you to focus on the client/server side of Error Telemetry while I work on the Updates service stuff which hasn't been very thoroughly designed just yet.
That would give you the opportunity to get your hands dirty with evergreen-client for sure!