Fwd: Gerrit Metrics - Wikitech-l

12 Oct 2012


      Interesting email coming through Chad about e tool being developed to 
retrieve metrics from Gerrit.
I wonder how this effort is doing next to gerrit-stats. Overlapping, 
complementarity... I will look further, but if the Gerrit experts in the 
house can have a look, all the better.
--
Quim
---------- Forwarded message ----------
From: Lundh, Gustaf Gustaf.Lundh@sonymobile.com
Date: Fri, Oct 12, 2012 at 7:30 AM
Subject: RE: Gerrit Metrics
To: Remy Bohmer linux@bohmer.net, Janne Hellsten jjhellst@gmail.com
Cc: Stephen Roberts stephen.roberts4@gmail.com, Repo and Gerrit
Discussion repo-discuss@googlegroups.com,
"jose.lobato@isis-papyrus.com" jose.lobato@isis-papyrus.com
For some of my Gerrit-metrics I'm using the Gerrit-event module in
Gerrit-trigger[1] to collect events through the stream-event SSH
interface.
I collect the interesting data and feed it to a Graphite instance.
This way I can plot real-time data in terms of:
Changes per hour (or minute) and also the rate of comments/merges/etc.
One of my colleagues has also created python interface for listening
and parsing the events. Not sure if it has been open-sourced yet.
[1] https://github.com/jenkinsci/gerrit-trigger-plugin
Best regards
Gustaf
-----Original Message-----
From: repo-discuss@googlegroups.com
[mailto:repo-discuss@googlegroups.com] On Behalf Of Remy Bohmer
Sent: den 29 december 2011 22:58
To: Janne Hellsten
Cc: Stephen Roberts; Repo and Gerrit Discussion;
jose.lobato@isis-papyrus.com
Subject: Re: Gerrit Metrics
Hi,
2011/12/29 Janne Hellsten jjhellst@gmail.com:
...
...
...
I've written Haskell code to talk to Gerrit via SSH and parse the
JSON responses to Haskell data structures.  This is pretty handy for
further data mining in Haskell.  Ping me if you're interested, I can
make the code available if someone finds it useful.
Here is the ping ;-)
I find it useful, where can I find the code?
You can find the GerritJson module here:
https://github.com/nurpax/gerrit-json
I only recently went back to Haskell so there are probably many ways
in which the code can be improved.
Thanks for sharing!
I will look into it in detail next year/week ;-)
Kind regards,
Remy
--
To unsubscribe, email repo-discuss+unsubscribe@googlegroups.com
More info at http://groups.google.com/group/repo-discuss?hl=en
--
To unsubscribe, email repo-discuss+unsubscribe@googlegroups.com
More info at http://groups.google.com/group/repo-discuss?hl=en