Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Automated Error Reporting for Mars Milestone Builds
+1, I'd love to have this feature not only for milestone builds. Several years ago at Xored we were trying to build a similar system for server-side error log collection and grouping, with additional collection of extra information like jre version, os name, memory settings, disk usage, but couldn't find enough resources to make it live.

Additional note – sometimes, even during email communication, people don't send error logs because they don't want to reveal their proprietary bundle IDs (so they don't want you to know their company/product name), or send logs with those ids are replaced by asterisks. So maybe having an option like "obfuscate non-eclipse bundles and class names" could potentially attract such users.

Ivan Inozemtsev


On Mon, Aug 11, 2014 at 1:33 AM, Konstantin Komissarchik <konstantin.komissarchik@xxxxxxxxxx> wrote:
+1

This tool can be made even more valuable to the broader community if it wasn't limited to org.eclipse errors. In fact, access to the system outside of org.eclipse namespace can be a perk of foundation membership.

Konstantin Komissarchik
Senior Development Manager
Eclipse Tools Group
Oracle

On Aug 10, 2014, at 3:53, Marcel Bruch <marcel.bruch@xxxxxxxxxxxxxx> wrote:

Hi cross-projects-issues,


the Mars release train is picking up speed again and I’d like to propose adding an error log reporting tool to the milestone builds that reports errors to a central logging service at eclipse.org. 

What’s cross-project’s take on this?
Do you see a need and would you agree to add this to the milestone builds?



The intension is obvious I think. Errors happen (especially during the milestone builds). The sad thing is that it usually takes weeks until a user recognizes them as such and reports them to Bugzilla – if ever. To help us to get notified about issues in the current code base and fixing them as quickly as possible, I’d like to add a log listener to the platform log which automatically sends error log entries to a server at eclipse.org.

The proposed user-workflow is pretty simple:
Whenever an error is logged to the Eclipse error log, that service checks whether it’s an error logged by an Eclipse plugin (by checking the plugin id starts with „org.eclipse“). If so, it opens a dialog asking the user for permission to send that error to our server (recommenders.eclipse.org) for further processing. For a brief summary of the UI, please see the wizard screenshot below.


On the server side, the error is logged and we (ATM me) are notified by email that there is something new to analyze. There is also a dashboard [1] that allows committers to review which errors have been logged in the past, say, 7 days and to analyze the submitted errors. If of interest, that system can be extended to send errors by email to selected committers based on some search criteria like containing „org.eclipse.your-project“ in a stacktrace etc.

For details about the submitted data, please study one of the example error log entries in [1]. It contains all data that would be sent.



To pick up the question from the beginning: What’s cross-project’s take on this? Should such a feature be added to the milestone builds? 
I sure that EF needs to give their permission, but the general question is whether we’d like to know (and get notified in such a way) about errors our users experience. From my experience only few people discuss on cross-projects. But maybe you can cast your voice in a mini-survey [2]?


Marcel





<error-reporting-wizard.png><Bildschirmfoto 2014-08-10 um 12.24.13.png>

_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Back to the top