Yes, we count events for each workspace separately. But IMO that's is OK.
It maybe not very convenient for testing purposes but not a big deal for
collecting real stats.
I included jbosstools-dev(a)lists.jboss.org to CC.
On 06/12/2014 02:24 AM, Radim Hopp wrote:
Hi!
I finally found what I was missing here... That this is workspace specific. I
often use different workspaces so it was hard for me to spot the reporting GET
request in error log (because it wasn't there :-D).
I know that typically user works with one (or some small ammount) workspace,
but he surely has to change that workspace from time to time ("broken"
workspace is not a nice thing :-D), which results into some data not being
sent.
I don't know how hard/possible would be to change this... Either to eclipse
instance specific (but this would suffer from almost (changing eclipse instance)
the same disatvantage as workspace-specific solution), or to OS user specific.
Maybe I'm beating a dead horse and work required to change this would be too
high price according to what we can get from it (few data not reported)
Is it worth it, or should I just go with it? :-D
Radim
On Wednesday, May 28, 2014 09:37:49 you wrote:
> Hi Radim,
>
> We check if there are some daily events which are ready to be sent at
> every event type registration (it's recommended to register an event
> type at plug-in startup) and also every 24 hours in case of long running
> Eclipse sessions.
> So it means that if Eclipse is closed earlier then the counted daily
> events will be sent at the next startup.
>
> On 05/28/2014 04:19 AM, Radim Hopp wrote:
>> Hi Alexey,
>> I've been looking on new features of usage reporting and one think isn't
>> completely clear to me. It's those events which are logged once per day.
>> If i understood it correctly, they are scheduled 24 hours after workbench
>> startup. What happens if workbench is closed earlier? Does it still send
>> the data in some shutdown job?
>> Thanks for explanation.
>> Radim