<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Apr 15, 2016 at 12:24 AM, Nadav Goldin <span dir="ltr"><<a href="mailto:ngoldin@redhat.com" target="_blank">ngoldin@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><div>Hi,<br></div>I've created an experimental dashboard for Jenkins at our Grafana instance:<br><a href="http://graphite.phx.ovirt.org/dashboard/db/jenkins-monitoring" target="_blank">http://graphite.phx.ovirt.org/dashboard/db/jenkins-monitoring</a><br></div><div>(if you don't have an account, you can enrol with github/google)<br></div><div><br></div></div></div></div></blockquote><div><br></div><div>Pretty nice!</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div></div>currently it collects the following metrics:<br></div>1) How many jobs in the Build Queue are waiting per slaves' label:<br><br></div><div>for instance: if there are 4 builds of a job that is restricted to 'el7' and 2 builds of another job <br>which is restricted to 'el7' in the build queue we will see 6 for 'el7' in the first graph. <br>'No label' sums jobs which are waiting but are unrestricted.<br><br></div><div>2) How many slaves are idle per label.<br></div><div>note that the slave's labels are contained in the job's labels, but not vice versa, as<br></div><div>we allow regex expressions such as (fc21 || fc22 ). right now it treats them as simple<br></div><div>strings.<br><br></div><div>3) Total number of online/offline/idle slaves<br><br>besides the normal monitoring, it can help us:<br></div><div>1) minimize the difference between 'idle' slaves per label and jobs waiting in the build queue per label. <br>this might be caused by unnecessary restrictions on the label, or maybe by the <br>'Throttle Concurrent Builds' plugin.<br></div><div>2) decide how many VMs and which OS to install on the new hosts.<br></div><div>3) in the future, once we have the 'slave pools' implemented, we could implement<br></div><div>auto-scaling based on thresholds or some other function.<br><br><br></div><div>'experimental' - as it still needs to be tested for stability(it is based on python-jenkins<br></div><div>and graphite-send) and also more metrics can be added(maybe avg running time<br></div><div>per job? builds per hour? ) - will be happy to hear.<br><br></div><div>I plan later to pack it all into independent fabric tasks(i.e. fab do.jenkins.slaves.show)<span class="HOEnZb"><font color="#888888"><br><br></font></span></div><span class="HOEnZb"><font color="#888888"><div><br>Nadav<br><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div> <br><br><br> <br></div></font></span></div>
<br>_______________________________________________<br>
Infra mailing list<br>
<a href="mailto:Infra@ovirt.org">Infra@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/infra" rel="noreferrer" target="_blank">http://lists.ovirt.org/mailman/listinfo/infra</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr"><div><div dir="ltr">Sandro Bonazzola<br>Better technology. Faster innovation. Powered by community collaboration.<br>See how it works at <a href="http://redhat.com" target="_blank">redhat.com</a><br></div></div></div></div>
</div></div>