Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Error reporter and third-party code

Am 24.07.2015 um 19:55 schrieb Max Rydahl Andersen <manderse@xxxxxxxxxx>:

On 24 Jul 2015, at 17:27, Marcel Bruch wrote:

I think those clients (which currently make ~28% of the error reports) should actually sign-up and subscribe to their error reports

How do I subscribe to error reports that are filtered ?

Support for this is limited. Check the Saphire alert [1] which listens to problems marked as „THIRD“. Note that the global filtering rules still apply (logged by an org.eclipse plugin, 3rd party class names likely anonymized).

- or set up their own error collection to review and fix their issues themselves.

...adding another layer of error reporting will give even worse end-user experience imo - i.e. how do I know that eclipse error reporter haven't reported it ?

A matter of implementation. There could be one listener that inspects the log event and delivers it different endpoints based on some criteria - or to the same endpoint (e.g if Eclipse would start collecting error reports for, say, its member companies - and for their commercial products / plugins?).



Codetrails GmbH
The knowledge transfer company

Robert-Bosch-Str. 7, 64293 Darmstadt
Phone: +49-6151-276-7092
Mobile: +49-179-131-7721

Managing Director: Dr. Marcel Bruch
Handelsregister: Darmstadt HRB 91940

Back to the top