A standard UUID. We generate it once per user-home. We use that information to allow searches like “Give me all error reports ±5 minutes around this error report” or to collect how many users actually hit a problem (to assess its severity) etc.
Which is a nice metric. I'm wondering if it is as relevant as how ofter the same error has been hit (regardless of user count).
The absolute number of all occurrences may be misleading if caused by just a single client.
Having both counts is probably what you’d like to see but this may cause a lot more traffic (if implemented naively)
- is the reporter id an "opt-in”?
Yes and no. You opt in to send error reports w/ a uuid when you enable AERI (announced and implemented so from day one).
So it is opt-in. I don't see any issues then.
OK, thanks for your assessment.
I’ll still wait (a week or so) for anyone vetoing before I start implementing that.
FWIW, there is a change in progress that allows users to generate a fresh UUID on every eclipse startup.
off-topic, but doesn't that make the metric mentioned above impossible?
Yes, that’s why it should not be the default. But we can recognize such a session UUID and do not count them.
cross-project-issues-dev mailing listcross-project-issues-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
The knowledge transfer company
Robert-Bosch-Str. 7, 64293 Darmstadt
Managing Director: Dr. Marcel Bruch
Handelsregister: Darmstadt HRB 91940