On Thu, Nov 29, 2012 at 4:05 PM, Diederik van Liere <dvanliere@wikimedia.org> wrote:

My main questions right now:

- Would vanadium or kraken be better suited for building this sooner than later (within a few weeks)

I definitely think that this is something for Kraken but would like David and Ottomata to chime in as well. 
 
- Would anyone like to help? (David, your guidance around coding the frontend visualization would be highly valued even if you don't have a day or two to personally throw at it)

I would say, let's use Etsy's statsd & graphite visualization solution, see http://github.com/etsy/statsd
statsd is  network daemon that runs on the Node.js platform and listens for statistics, like counters and timers, sent over UDP and sends aggregates to one or more pluggable backend services like Graphite and posssibly also Ganglia. Very little coding involved :)

While some extracted data will certainly go into graphite.wikimedia.org for aggregation with the edge cache performance timing data already there, this doesn't at all map to what I have in mind.

This needs to go into a more traditional non-time series data store with advanced filtering / query / sort capabilities across all axis.  That better fits with client side visualization, for both graph and textual targets.