On Tue, May 4, 2010 at 13:05, Ran Tavory <ran...@gmail.com> wrote: > IMO there's a good case for both external monitoring tools and per-host > minimalistic interface but I see Eric's point that every piece of code will > require its maintenance. A cluster monitoring tool is definitely required. > An embedded one has two nice properties: > 1. It works out of the box > 2. If I want to know NOW what's going on on the host, I don't have to poll > like crazy (or wait 5 minutes for the next sample), I can just open the > browser and see. > > I'll see if I can get something simple running and ping back, but I can't > commit on a timeline. > Is adding jetty acceptable? Any other preferences?
I agree: there is a place for both types of solutions. contrib is probably best place (for both). IMO: jetty > tomcat, especially from the point of embedding. Gary, > > > On Tue, May 4, 2010 at 8:49 PM, Anthony Molinaro < > antho...@alumni.caltech.edu> wrote: >
