<div dir="ltr">Hi Karanbir,<div><br></div><div>Thanks for the email . Some initial thoughts. </div><div><br></div><div><u>Tests</u>:</div><div>1. No. of commits across the test suite. Simple things like git log --since < > can be pumped into graphite . You'll get an understanding of how many people are committing and how many requests are pending .</div>
<div>2. test suite runs - No of tests that fail in versions 5 and 6 and across several of the setups you have. This can be just the number .</div><div>3. We could one per package and details of that </div><div>Eg, package.httpd.tests.success - 4</div>
<div> package.httpd.tests.failure - 1 </div><div>4. Other metrics that you need to identify stability of test suites . </div><div><br></div><div>I have a few things around querying below ( either csv or json ) </div>
<div><br></div><div><u>Deploys</u>:</div><div>1. Success/failures based on platforms and mode of deploy.</div><div>Example: You can dump simple metrics back into graphite with 1 indicating success and 0 failure and create a hierarchy as follows: ( This is just an example) </div>
<div><br></div><div>deploy.kvm.64bit.http.success </div><div>deploy.kvm.64bit.nfs.success<br></div><div>deploy.xen.32bit.http.success </div><div>etc</div><div><br></div><div>and we could write queries to get the Json api to see how deploys across kvm(Eg. deploy.kvm.*.*.success) machines have happened over X days and maybe alert via Zabbix based on what we think it suitable. Graphite would just chart it and we'll have to have something sitting on top of it but having said that sending data to graphite( with statsd on top) is simple which is a point to consider. </div>
<div><br></div><div>We've used this behavior for chef client runs across 200 odd machines at work and its worked really well for us. </div><div><br></div><div>We can have slightly more fancy UI with graphene showing metrics of your choice:</div>
<div><a href="http://jondot.github.com/graphene/">http://jondot.github.com/graphene/</a> <br></div><div><br></div><div>Mamu</div><div><br></div><div>ps: I briefly read about stash board after you wrote about it but have not tried it .</div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Mar 15, 2013 at 12:05 AM, Karanbir Singh <span dir="ltr"><<a href="mailto:mail-lists@karan.org" target="_blank">mail-lists@karan.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">hi mamu,<br>
<div class="im"><br>
On 03/13/2013 06:05 PM, Madhurranjan Mohaan wrote:<br>
> Stashboard sounds good . We could also post messages to a graphite instance<br>
> based on what we metrics we need and it'll give you nice graphs ,especially<br>
> when you want to compare it with other metrics (in case they are<br>
> comparable). +1 for the idea.<br>
<br>
</div>I had a poke around stashboard, and its pretty complicated and<br>
cumbersome if we want to run it offline (ie. not on appengine ); there<br>
are some other options as well.<br>
<br>
Having seen the deploy + test scenarious we run, what sort of metrics do<br>
you think we should shovel graphite way ?<br>
<div class="im HOEnZb"><br>
--<br>
Karanbir Singh<br>
+44-207-0999389 | <a href="http://www.karan.org/" target="_blank">http://www.karan.org/</a> | <a href="http://twitter.com/kbsingh" target="_blank">twitter.com/kbsingh</a><br>
GnuPG Key : <a href="http://www.karan.org/publickey.asc" target="_blank">http://www.karan.org/publickey.asc</a><br>
</div><div class="HOEnZb"><div class="h5">_______________________________________________<br>
CentOS-devel mailing list<br>
<a href="mailto:CentOS-devel@centos.org">CentOS-devel@centos.org</a><br>
<a href="http://lists.centos.org/mailman/listinfo/centos-devel" target="_blank">http://lists.centos.org/mailman/listinfo/centos-devel</a><br>
</div></div></blockquote></div><br></div>