|[cross-project-issues-dev] [aeri] Introducing (Custom) Error Report Processors
the upcoming version of AERI will allow to run client-side analyses before an error report is send.
For example, when a ClassNotFoundException is logged, AERI will run an analyzer that
The results of these analyses are added to the error report as "auxiliary information” automatically (requires user consent).
The Buildship team requested a means to add the Gradle version to error reports that mention Buildship somewhere. The Oomph team asked for means to run special analysis for FileNotFoundExceptions to detect whether these errors may be caused by an eager antivirus scanner. Both can be implemented using this API.
AERI will provide some "common processors” that add
to an error report on demand. We may also take this a step further to allow users to attach screenshots or code snippets to an error report.
The analyzers will be added to the review dialog as outlined below and can be de/activated in one click. The server can also demand auxiliary information which will be automatically added to the report (after user consent):
Every project will be able to register their own client-side analyses via an extension point. The exact details are not yet settled but I’d like to inform cross-projects early in the process to gather your requirements. If you have a requirement or feature request, please let me/us know in bug 496656 .
The knowledge transfer company
Robert-Bosch-Str. 7, 64293 Darmstadt
Managing Director: Dr. Marcel Bruch
Handelsregister: Darmstadt HRB 91940
Back to the top