---
title: "Just Open-Sourced: Send Jenkins (Hudson) Stats to Graphite"
summary: "Describing a newly-open-sourced script to track Jenkins build capacity in Graphite."
date: 2012-01-13
authors: [yoav-shapira]
topics: [DevEx]
canonical: https://product.hubspot.com/blog/bid/81142/just-open-sourced-send-jenkins-hudson-stats-to-graphite
cover:
  scene: just-open-sourced-send-jenkins-hudson-stats-to-graphite
  alt: "In a laundromat with every machine busy, people wait with their baskets while a pencil charts the wait, until a new washer with a bow rolls in."
---

At HubSpot we use [Graphite](http://graphite.wikidot.com/) for most of our operational graphing needs, tracking such things as server uptime, response times, response codes (errors, etc.), cache layer capacity and hit rates, and more.

![The Jenkins logo: a cartoon butler in a bow tie holding a napkin.](/assets/blog/just-open-sourced-send-jenkins-hudson-stats-to-graphite/jenkins-logo.png)

We also use [Jenkins](http://jenkins-ci.org/) (formerly Hudson) for continuous integration, since we like to deploy very often.  Jenkins, like all systems, can have capacity bottlenecks where there are no build executors available to run a build.  This results in delays that frustrate developers and slow us down. &#x20;

But how often does it happen?  When should we add Jenkins nodes to our cluster?

One of our developers, [Jeremy Katz](https://twitter.com/#!/katzj), has recently written a script to track just this using the [Jenkins API](https://wiki.jenkins-ci.org/display/JENKINS/Remote+access+API), and push the results to Graphite for easy viewing and analysis.  He went a step further, open-sourcing his script under the Apache License.

Read more information, and enjoy the script, on [Jeremy's blog](http://velohacker.com/hubspot/graphing-jenkins-statistics/). &#x20;
