[eclipse] Including automated error reporting in the Eclipse tooling

[Robert Munteanu <rm...@adobe.com>]

Hi,


The automated error reporting project used by the Eclipse Foundation (
see [1] for some background ) has now been opened up for all third
party Eclipse plug-ins [2] , allowing them to gather error reports and
store them on a central instance, hosted by Ctrlflow/Codetrails.

This would be very useful in allowing us to quickly understand what
problems occur when the plug-ins are used and getting to reach users
faster.

Before setting up an account and configuring the plug-in I would like
to see what others think about this.

Briefly, as an Eclipse user:

- I am asked if I want to enable error reporting for my instance and
the specific 'provider' - such as the Eclipse Foundation or Apache
Sling
- whenever an error occurs, I am notified via a popup and can choose to
either ignore the issue, or send it alongside with optional comments
- I am always able to inspect the details of the report before
submitting

The full details of the agreement are at [3], which is what I would
agree to when setting up an account.

Thoughts?

Robert

[1]: https://blog.ctrlflow.com/byo-aeri-in-eclipse-neon/
[2]: https://blog.ctrlflow.com/free-error-reporting-service-for-eclipse
/
[3]: https://www.ctrlflow.com/assets/media/pdfs/automated-error-reporti
ng/ctrlflow-automated-error-reporting-terms.pdf

Re: [eclipse] Including automated error reporting in the Eclipse tooling

[Johannes Dorn <jo...@codetrails.com>]

Hi,

I am working for Codetrails on Ctrlflow Automated Error Reporting. Let
me address your questions below.

On 2017-02-27 16:49 (+0100), Robert Munteanu wrote:
> On Mon, 2017-02-27 at 16:47 +0100, Stefan Egli wrote:>
> > What comes to mind first is legal. And who would have access to the>
> > error>
> > reports at Ctrlflow/Codetrails?>

> As for access to the error reports, my understanding is that only>
> accounts explicitly allowed to access the error reports would get that>
> data.>

You can create user accounts that can review and act on error reports.
We call those users "reviewers".
They have full access to the error reports.

Users that submit error reports have access to their own reports only.

The Codetrails team has administrative access to the system in order to
do troubleshooting or provide technical support.
Thus, we also have access to the error reports.

If you are interested in what information is included in the error
reports, this is explained in detail at [1].
To summarize, users can but do not have to include their name and email
address.
They can also anonymize all stack trace elements that are not part of
Apache Sling or org.eclipse.*.

The server is hosted in Germany.

I hope this addresses your legal concerns.
As an example, Pivotal have included Ctrlflow Automated Error Reporting
in their Spring Tool Suite already; their legal disclaimer can be found
at [2]

I am not familiar with Apache Sling (yet, it looks great!), so I assume
you are interested in including Ctrlflow in your Eclipse plugins.
You could also include it in any other application as it is very easy to
extend configurations of logging frameworks like Logback, Log4J, or
java.util.logging [3] to send reports to your error reporting service.

Let me know if you have more questions.

Cheers
Johannes

[1]
https://www.ctrlflow.com/automated-error-reporting/docs/misc/sent-data.html
[2] http://docs.spring.io/sts/nan/v382/SpringToolSuite-AERI-Details.html
[3] https://github.com/codetrails/ctrlflow-aer-client

-- 
Johannes Dorn

Codetrails GmbH
The knowledge transfer company

Robert-Bosch-Str. 7, 64293 Darmstadt
Tel: +49 6151 2767092
http://www.codetrails.com

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

Re: [eclipse] Including automated error reporting in the Eclipse tooling

[Robert Munteanu <ro...@apache.org>]

On Mon, 2017-02-27 at 16:47 +0100, Stefan Egli wrote:
> Hi Robert,
> 
> Sounds very useful indeed.
> 
> What comes to mind first is legal. And who would have access to the
> error
> reports at Ctrlflow/Codetrails?

Right, I'm not sure what legal involvement would be here. That's why
I'm posting.

As for access to the error reports, my understanding is that only
accounts explicitly allowed to access the error reports would get that
data.

Robert

> 
> Cheers,
> Stefan
> 
> On 27/02/17 15:59, "Robert Munteanu" <rm...@adobe.com> wrote:
> 
> > Hi,
> > 
> > 
> > The automated error reporting project used by the Eclipse
> > Foundation (
> > see [1] for some background ) has now been opened up for all third
> > party Eclipse plug-ins [2] , allowing them to gather error reports
> > and
> > store them on a central instance, hosted by Ctrlflow/Codetrails.
> > 
> > This would be very useful in allowing us to quickly understand what
> > problems occur when the plug-ins are used and getting to reach
> > users
> > faster.
> > 
> > Before setting up an account and configuring the plug-in I would
> > like
> > to see what others think about this.
> > 
> > Briefly, as an Eclipse user:
> > 
> > - I am asked if I want to enable error reporting for my instance
> > and
> > the specific 'provider' - such as the Eclipse Foundation or Apache
> > Sling
> > - whenever an error occurs, I am notified via a popup and can
> > choose to
> > either ignore the issue, or send it alongside with optional
> > comments
> > - I am always able to inspect the details of the report before
> > submitting
> > 
> > The full details of the agreement are at [3], which is what I would
> > agree to when setting up an account.
> > 
> > Thoughts?
> > 
> > Robert
> > 
> > [1]: https://blog.ctrlflow.com/byo-aeri-in-eclipse-neon/
> > [2]: https://blog.ctrlflow.com/free-error-reporting-service-for-ecl
> > ipse
> > /
> > [3]: https://www.ctrlflow.com/assets/media/pdfs/automated-error-rep
> > orti
> > ng/ctrlflow-automated-error-reporting-terms.pdf
> 
> 

Re: [eclipse] Including automated error reporting in the Eclipse tooling

[Stefan Egli <st...@apache.org>]

Hi Robert,

Sounds very useful indeed.

What comes to mind first is legal. And who would have access to the error
reports at Ctrlflow/Codetrails?

Cheers,
Stefan

On 27/02/17 15:59, "Robert Munteanu" <rm...@adobe.com> wrote:

>Hi,
>
>
>The automated error reporting project used by the Eclipse Foundation (
>see [1] for some background ) has now been opened up for all third
>party Eclipse plug-ins [2] , allowing them to gather error reports and
>store them on a central instance, hosted by Ctrlflow/Codetrails.
>
>This would be very useful in allowing us to quickly understand what
>problems occur when the plug-ins are used and getting to reach users
>faster.
>
>Before setting up an account and configuring the plug-in I would like
>to see what others think about this.
>
>Briefly, as an Eclipse user:
>
>- I am asked if I want to enable error reporting for my instance and
>the specific 'provider' - such as the Eclipse Foundation or Apache
>Sling
>- whenever an error occurs, I am notified via a popup and can choose to
>either ignore the issue, or send it alongside with optional comments
>- I am always able to inspect the details of the report before
>submitting
>
>The full details of the agreement are at [3], which is what I would
>agree to when setting up an account.
>
>Thoughts?
>
>Robert
>
>[1]: https://blog.ctrlflow.com/byo-aeri-in-eclipse-neon/
>[2]: https://blog.ctrlflow.com/free-error-reporting-service-for-eclipse
>/
>[3]: https://www.ctrlflow.com/assets/media/pdfs/automated-error-reporti
>ng/ctrlflow-automated-error-reporting-terms.pdf