Hi! I was working on a separate monitoring client, and not a per-node approach.
At the time, we talked on having a single server that queries the nodes on a Cassandra cluster. There's some discussions on the list, about technologies being used, etc. I was pretty busy these last weeks (and some days out of town), I'm actually working on a python based UI on the server side, and got some time for testing pylons and tornado for two different approaches, one with synchronous and one with asynchronous requests. Also, someone just told me of another JMX/Rest interface, different from the one I was going to use (and adapt). You can find an architecture draft here: http://www.estudioquadra.com/gsoc2010/ At first time Django was proposed (just for being the most well-known), but it's oversized, and later we decided to go with Pylons. On Tue, May 4, 2010 at 11:21 AM, Eric Evans <eev...@rackspace.com> wrote: > On Tue, 2010-05-04 at 08:41 +0300, Ran Tavory wrote: >> How about the following compromise: >> Add a simple web server to each node with only one simple servlet that >> simply spits out all JMX stats on one page. Not fancy, no graphs, >> simply the same values you can get from jconsole, but on a web page. >> To me it seems like a fair tradeoff b/w maintenance and easier out of >> the box management. Shooting up jconsole for each server is >> cumbersome, at least in the environment I work in (firewalls, high >> latency etc) so a web interface can be nice. > > It still seems superfluous to me, but I'd be open to something > fire-and-forget (i.e. wouldn't need updating each time something new was > added). > > -- > Eric Evans > eev...@rackspace.com > >
