Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "EPP/Obsolete/Logging"
(Replace "Submitted Information" with link to server side documentation.) |
m |
||
| Line 1: | Line 1: | ||
| − | == | + | == Sign Up for Eclipse.org Projects == |
| − | + | Every Eclipse project can sign up to receive error reports. To do so, file a request in AERI's Bugzilla component (https://bugs.eclipse.org/bugs/enter_bug.cgi?product=EPP) | |
| + | == Sign Up for Non-Eclipse.org Projects == | ||
| + | Non-Eclipse.org projects can signup for free using an error reporting service hosted by Codetrails. Check out [https://ctrlflow.com/automated-error-reporting/?utm_source=eclipse&utm_campaign=free&utm_medium=wiki this website] for details. | ||
| − | == | + | == Documentation == |
| − | + | ||
| − | + | Check out the [https://ctrlflow.com/automated-error-reporting/docs/ Ctrlflow manual]. | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
== Contact == | == Contact == | ||
| − | To get in touch | + | To get in touch, post your questions to the [https://www.eclipse.org/forums/index.php/f/69/ EPP forum]. Preferably you prefix your post's subject with '''[aeri] your subject title''' for questions about the automated error reporting. |
If you use Mattermost, check out the [https://mattermost-test.eclipse.org/eclipse/channels/epp-aeri Mattermost EPP AERI channel]. | If you use Mattermost, check out the [https://mattermost-test.eclipse.org/eclipse/channels/epp-aeri Mattermost EPP AERI channel]. | ||
| Line 34: | Line 22: | ||
* http://download.eclipse.org/technology/epp/logging/head/ | * http://download.eclipse.org/technology/epp/logging/head/ | ||
| − | + | URLs may change without further notice. If you need stable URLs, use the annual release train update sites. | |
| − | + | ||
== Contributing == | == Contributing == | ||
| Line 45: | Line 32: | ||
The automated error reporting disables itself if it cannot detect a system property called '''eclipse.buildId'''. This is usually the case if you execute a test suite with Maven Tycho. If you want the automated error reporting to stay enabled, set the system property to '''‑Declipse.buildId=some-id''' in your Eclipse launch configuration. | The automated error reporting disables itself if it cannot detect a system property called '''eclipse.buildId'''. This is usually the case if you execute a test suite with Maven Tycho. If you want the automated error reporting to stay enabled, set the system property to '''‑Declipse.buildId=some-id''' in your Eclipse launch configuration. | ||
| − | In the case you run your test suite in a 'normal' eclipse installation which already has the buildId, you can disable error reporting completely by setting the system property '''‑Dorg.eclipse.epp.logging.aeri | + | In the case you run your test suite in a 'normal' eclipse installation which already has the buildId, you can disable error reporting completely by setting the system property '''‑Dorg.eclipse.epp.logging.aeri.skipReports=true'''. |
| − | Note: In Aeri | + | Note: In Aeri 1.x the property name was '''org.eclipse.epp.logging.aeri.ui.skipReports'''. |
== Enable additional debug output == | == Enable additional debug output == | ||
| Line 68: | Line 55: | ||
=== Can I collect errors for my own Eclipse plug-ins? === | === Can I collect errors for my own Eclipse plug-ins? === | ||
| − | Yes | + | Yes. AERI 2.x offers an Eclipse extension point where projects can register their own servers/endpoints via plugin.xml. See [https://www.youtube.com/watch?v=TDSv9Tm7hGA this webinar] for detailed step-by-step introduction. |
=== Can I use error reporting in my own Eclipse RCP applications? === | === Can I use error reporting in my own Eclipse RCP applications? === | ||
| − | Yes | + | Yes. Watch [https://www.youtube.com/watch?v=TDSv9Tm7hGA this webinar] for details and check out the examples in the git repository. |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
[[Category:EPP]] | [[Category:EPP]] | ||
Revision as of 04:43, 13 March 2017
Contents
Sign Up for Eclipse.org Projects
Every Eclipse project can sign up to receive error reports. To do so, file a request in AERI's Bugzilla component (https://bugs.eclipse.org/bugs/enter_bug.cgi?product=EPP)
Sign Up for Non-Eclipse.org Projects
Non-Eclipse.org projects can signup for free using an error reporting service hosted by Codetrails. Check out this website for details.
Documentation
Check out the Ctrlflow manual.
Contact
To get in touch, post your questions to the EPP forum. Preferably you prefix your post's subject with [aeri] your subject title for questions about the automated error reporting.
If you use Mattermost, check out the Mattermost EPP AERI channel.
Update Sites
The update sites are at the moment hosted here:
- http://download.eclipse.org/technology/epp/logging/stable/
- http://download.eclipse.org/technology/epp/logging/milestones/
- http://download.eclipse.org/technology/epp/logging/head/
URLs may change without further notice. If you need stable URLs, use the annual release train update sites.
Contributing
EPP Logging maintains an Oomph profile that provisions a complete workspace with code formatter settings etc. Simply start the Oomph installer, switch to advanced mode, select the EPP -> Logging profile and click install.
Disabling AERI in builds and runtime Eclipse
The automated error reporting disables itself if it cannot detect a system property called eclipse.buildId. This is usually the case if you execute a test suite with Maven Tycho. If you want the automated error reporting to stay enabled, set the system property to ‑Declipse.buildId=some-id in your Eclipse launch configuration.
In the case you run your test suite in a 'normal' eclipse installation which already has the buildId, you can disable error reporting completely by setting the system property ‑Dorg.eclipse.epp.logging.aeri.skipReports=true.
Note: In Aeri 1.x the property name was org.eclipse.epp.logging.aeri.ui.skipReports.
Enable additional debug output
AERI can write additional debug information to the error log, e.g.,:
- Network exceptions on startup.
- Explanation why an error log event was ignored.
To enable the debug output,
- Open ${eclipse.working.dir}/.options and insert the line:
org.eclipse.epp.logging.aeri.core/debug=true
- On Mac it's .../Eclipse.app/MacOs/.options - next to the eclipse executable.
- In your eclipse.ini add the following line before the -vmargs section:
-debug
- Restart Eclipse.
Visit this page for details on how to use Platform debug tracing facility.
Submitted Information
In order to provide you with enough information to identify and fix problems, data needs to be sent to your Automated Error Reporting service. To review which information is submitted, please visit the Ctrlflow Automated Error Reporting Documentation.
FAQ
Can I collect errors for my own Eclipse plug-ins?
Yes. AERI 2.x offers an Eclipse extension point where projects can register their own servers/endpoints via plugin.xml. See this webinar for detailed step-by-step introduction.
Can I use error reporting in my own Eclipse RCP applications?
Yes. Watch this webinar for details and check out the examples in the git repository.