At We Heart It, we collect a lot of data in several graphs & dashboars. But the graph data alone might not always be enough, sometimes you need context about what actually changed to know why the graph changed (like a big change on response times).

Thankfuly, Graphite now supports events (although is not very well documented), so it's actually really easy to display when the code was deployed and add some information about the deploy itself.

We use Graphana for most of our dashboards. It is an amazing graphing tool, that gets data from Graphite and displays it in a really nice way. You should really try it.

The Basics

First we need to create an event. This is easily done by POSTing some simple JSON:

curl -X POST -d \
'{"what": "Code deploy", "tags": "rails-deploy", data: "commit information"}'

Then we need to enable Graphana annotations and display the rails-deploy tag on our dashboard. The result will look like this:

Deploy Events

Using Capistrano

Since we use Capistrano to deploy our apps, we can automatically create deploy events every time a deploy finishes, here's our task:

after "deploy", "graphite:mark_deploy"

namespace :graphite do
  task :mark_deploy do
    commit_information = `git log -n 1 --pretty=format:'%h - %s - %an' --abbrev-commit`

    auth = { username: "foo", password: "bar" }
    body = {
      what: "rails code deployed.",
      tags: "rails-deploy",
      data: "#{fetch(:branch)} deployed at #{} ( #{commit_information} )"
    }"", basic_auth: auth, body: body.to_json )
    puts "Deploy sent to Graphite."

The commit_information information will give you something like this:

68305ff - Allow wildcard increment/decrement on stats counters. - Nicolás Hock Isaza

You can use this information as a starting point when things go wrong with a deploy.

This is a very easy thing to add and gives you a lot of extra context around your graphs, I found it really useful when we added it for the first time (and use it a lot today as well).