Buttercup Games – Level 2: Buttercup Go data

Buttercup Go is thriving 4,234 people have played the game and lots of data is being generated. In this post I’ll walk through some of the data we are generating.

Splunk ButtercupGo Overview

The data includes web, OS, load balancer, network, firewall, other AWS data, etc. There are a few other data sources I want to point out specifically.

Authentication Data

We wanted to allow users to play right away, without the need to sign up. Auth0 was a perfect choice. It was quite easy to use and gave us everything we needed. Not only did it allow many authentication options (think Google, Facebook, Twitter, LinkedIn, etc) but Auth0 also generated great data and could send directly into Splunk. Here was the breakdown of how people chose to login.

Screen Shot 2016-09-28 at 5.34.40 PM

Game data

If you were at .conf2015 last year you may remember we asked the audience to shake their phones, allowing us to collect accelerometer data via the HTTP Event Collector. This year we again collected HEC data but different fields. Here is what a part of an event looks like when you play a game:


This is the info we use to populate the dashboards around the conference to show information like top score, games played (deaths), total flaps, even total time played.

dashboard ButtercupGo logins playtime

Dev data

The game data isn’t the only data we collected via HEC. We also collected all events from our github repo using a webhook! This is only possible because Base Authentication was added to HEC in 6.5 (HEC now also supports indexed fields).  Now go get your git data into Splunk!

Splunk dev data manage webhooks

Nate McKervey

Posted by