News for hackers. Stuff that matters.
Re:Cube: time series visualization (MongoDB + Node + D3) by bryanh on Thursday September 15, 2011 @04:39PM (#3002020)
This kind of rekindles an interest I had in building a web app that was at its core a data vacuum.

You sent it whatever data you like, be that timestamps, integers, floats, arbitrary strings, etc... and it would let you build an intelligent dashboard displaying the data however you like.

Re:Cube: time series visualization (MongoDB + Node + D3) by xyzzyb on Thursday September 15, 2011 @09:44PM (#3002835)
Sounds like GoodData (http://www.gooddata.com/), which is great! Competition drives innovation.
Re:Cube: time series visualization (MongoDB + Node + D3) by xnxn on Thursday September 15, 2011 @07:03PM (#3002466)
I say go for it! It sounds very useful (and has an obvious monetization strategy if you wanted to make a business out of it).
Re:Cube: time series visualization (MongoDB + Node + D3) by khafra on Friday September 16, 2011 @09:03AM (#3004263)
Sounds like Splunk, to me.
Re:Cube: time series visualization (MongoDB + Node + D3) by pedoh on Thursday September 15, 2011 @04:45PM (#3002049)
We're currently using Graphite ( http://techblog.appnexus.com/2011/metrics/ ) and loving it, but using MongoDB is an interesting spin.

I'd love to see some performance benchmarks and see how many datapoints you can pump in and out of Cube. We've been collecting about 1 million metrics every minute on a speedy dual proc / quad core box backed with SSDs for storage.

Re:Cube: time series visualization (MongoDB + Node + D3) by noahnoahnoah on Thursday September 15, 2011 @05:07PM (#3002147)
This looks fantastic. From the short demo, nice UI for setting up charts, and the visualizations produced are quite nice as well.

The only downside to something like this (and Graphite, etc.) is that you can only visualize data that you store in Cube (if I understand correctly). That's great for things you sample yourself, but what if you want to compare something you sampled yourself with something from New Relic or another data source? Cube looks to go a step further than Graphite in allowing for easier custom visualizations, but data is still a one-size-fits-all thing. You can write an emitter/parser that grabs the data and stores it in Cube, but there's a huge amount of duplication (and essentially polling then).

I think a better architecture is to separate data storage/acquisition from visualization. Establish a set of standards for data interfaces that specify the output they provide, and build your visualization on top of that. Then, your interfaces can be API wrappers, mysql connections, a mongo-db based storage system, a redis-backed storage system, etc.

Re:Cube: time series visualization (MongoDB + Node + D3) by mbostock on Thursday September 15, 2011 @05:41PM (#3002240)
True, but collecting the data into a single store makes it easier to analyze. If you want to construct visualizations (or perform analysis) with data from different back-ends, you can do that using Cube’s API. I do like your idea of establishing standards for data interfaces, but I wonder how hard it would be to put into practice.
Re:Cube: time series visualization (MongoDB + Node + D3) by ojilles on Thursday September 15, 2011 @05:55PM (#3002275)
Doesnt that not simply already exist with RRDTool?
Re:Cube: time series visualization (MongoDB + Node + D3) by dgudkov on Friday September 16, 2011 @11:49AM (#3004923)
We made a tool for annotating time series -- it is intended for keeping remarks with explanations of influencing factors. Not that sophisticated but does what it does - http://explainum.com
Re:Cube: time series visualization (MongoDB + Node + D3) by scottostler on Thursday September 15, 2011 @04:20PM (#3001955)
Looks promising. I need to put together a dashboard, and this might be how I do it.

As an aside, it's always great to see more usage of PEG.js.

Re:Cube: time series visualization (MongoDB + Node + D3) by wuster on Thursday September 15, 2011 @06:48PM (#3002430)
I love this spirit of sharing and collaboration spurred by git/github. One nice side effect of adopting these open source libs (and not re-invent the wheel in house) is that we'll all have transferrable skills between companies in this space. I like this positive trend.
Re:Cube: time series visualization (MongoDB + Node + D3) by mnutt on Thursday September 15, 2011 @05:04PM (#3002132)
This is very, very cool. I've wanted something like this for a long time.

Running it, I'm having some issues loading pages that I think has something to do with caching static assets. Why not use an existing static file library?

Re:Cube: time series visualization (MongoDB + Node + D3) by mnutt on Friday September 16, 2011 @12:53AM (#3003247)
To answer my own question, it's because the author is doing asset bundling.
Re:Cube: time series visualization (MongoDB + Node + D3) by croddin on Thursday September 15, 2011 @04:35PM (#3002007)
This is almost exactly like something that I've been wanting to build!
Re:Cube: time series visualization (MongoDB + Node + D3) by ojilles on Thursday September 15, 2011 @04:45PM (#3002050)
It would be great to support something that shows the variation in the data for this stuff (average/median for response times is a notoriously bad idea).

Other than that, love it!

Re:Cube: time series visualization (MongoDB + Node + D3) by mwsherman on Thursday September 15, 2011 @05:28PM (#3002214)
Impressive. Suspect we’ll see folks rolling their own Chartbeats.
Re:Cube: time series visualization (MongoDB + Node + D3) by gourneau on Thursday September 15, 2011 @05:06PM (#3002139)
I wish they would have used ProtoVis with DataMarket's IE Shim

http://blog.datamarket.com/2011/06/22/protovis-support-inter...

Yes Protovis is no longer maintained, but here is a good post defending it: http://blog.datamarket.com/2011/09/12/the-protovis-stays/

And used Socket.IO for comm (they might)

However, it is lovely, I am going try it out :)

Re:Cube: time series visualization (MongoDB + Node + D3) by mrkurt on Thursday September 15, 2011 @05:07PM (#3002144)
The guy who wrote it is the author of d3, which might explain why they used d3. Plus, d3 is awesome.
Re:Cube: time series visualization (MongoDB + Node + D3) by paulirish on Thursday September 15, 2011 @05:31PM (#3002225)
Mike Bostock (creator of Protovis and D3) now works at Square, which helps explain this release from them. :)
Re:Cube: time series visualization (MongoDB + Node + D3) by hermanjunge on Thursday September 15, 2011 @04:19PM (#3001951)
Love It! I'm seeing it in my stack, connected in the cloud where apps send their data to the DB via rabbitMQ, to make monitors...
Re:Cube: time series visualization (MongoDB + Node + D3) by friggeri on Thursday September 15, 2011 @04:21PM (#3001961)
Believe it or not, I am actually developing exactly the same thing. I guess I'll use Cube then !
[deleted]
Re:Cube: time series visualization (MongoDB + Node + D3) by moe on Thursday September 15, 2011 @05:39PM (#3002232)
Yes, you missed that this has nothing in common with RRDTool other than that both happen to deal with timeseries data.
Re:Cube: time series visualization (MongoDB + Node + D3) by mildweed on Thursday September 15, 2011 @11:06PM (#3003034)
Did somebody say Time Cube?