We're going to have to make some decisions pretty soon about CAS4 if we're looking to include monitoring in CAS4, so please continue to post anything that you guys can think of to this thread. Suggestions are always welcome :-) We don't currently have any huge requirements for monitoring so we're gong to be relying on you guys (no pressure ;-)).
Thanks -Scott -Scott Battaglia PGP Public Key Id: 0x383733AA LinkedIn: http://www.linkedin.com/in/scottbattaglia On Wed, Jan 14, 2009 at 1:58 PM, J. David Beutel <[email protected]> wrote: > Yes, it looks generic (i.e., complicated) and requires a Hyperic server, > which will take resources (JBoss + database), although it's FOSS (for > the non-enterprise edition). > > The local Hyperic agent can monitor JVMs via JMX, like JConsole/VisualVM > can, but through the Hyperic server to record in the database and view. > Also, it has app-specific plugins, e.g., for Tomcat, which can provide > app-specific stats and auto-discovery. So, a CAS-monitoring plugin for > Hyperic seems possible, especially if you are already running a Hyperic > server. > > However, I'm still just trying out Hyperic, so I don't know yet if I'd > recommend it for this kind of monitoring. > > > Andrew Feller wrote: > > Isn't Hyperic a generic machine monitoring tool? I believe we use that > on > > our servers to keep track of whether they are up. I am interested in how > > this can be applied to an application. The only downside is whether you > > need to setup the Hyperic server or not and what costs are associated. > > > > > > On 1/13/09 10:03 PM, "J. David Beutel" <[email protected]> wrote: > > > > > >> Looking at using Hyperic for this. No conclusions yet, however... > >> > >> > >> Scott Battaglia wrote: > >> > >>> We already keep track of statistics via Inspektr (min, max, average, > >>> and time response time I believe). > >>> > >>> Right now, I'm attempting to mostly gather > >>> feedback/requirements/recommendations on monitoring and find out some > >>> available libraries. If you have any info, please feel free to share > :-) > >>> > >>> -Scott > >>> > >>> -Scott Battaglia > >>> PGP Public Key Id: 0x383733AA > >>> LinkedIn: http://www.linkedin.com/in/scottbattaglia > >>> > >>> > >>> On Mon, Jan 12, 2009 at 9:54 AM, Andrew Feller <[email protected] > >>> <mailto:[email protected]>> wrote: > >>> > >>> I am glad to hear that CAS monitoring is being considered for CAS4! > =) > >>> > >>> How were you thinking about incorporating this into CAS4? What > >>> areas of CAS performance should be monitored? Tickets granted? > >>> Cleaning / expiration of tickets? Activity related to individual > >>> services or users? I ask because Java Simon seems pretty > >>> simplistic and have trouble seeing how it would be used. I notice > >>> Java Simon mention JMX in a number of places, which I assume means > >>> they register themselves with the Mbean server and you can view > >>> this information via jconsole. > >>> > >>> > >>> > >>> > >>> > >>> On 1/12/09 8:39 AM, "Scott Battaglia" <[email protected] > >>> <mailto:[email protected]>> wrote: > >>> > >>> has anyone looked at Java Simon before as a potential tool for > >>> offering some monitoring of CAS servers? (i.e. for CAS4): > >>> > >>> http://code.google.com/p/javasimon/ > >>> > >>> If you have any thoughts or opinions on this or any other > >>> tool, please let me know. > >>> > >>> -Scott > >>> > >>> -Scott Battaglia > >>> PGP Public Key Id: 0x383733AA > >>> LinkedIn: http://www.linkedin.com/in/scottbattaglia > >>> > >>> > >>> > ------------------------------------------------------------------------ > >>> _______________________________________________ > >>> cas-dev mailing list > >>> [email protected] <mailto:[email protected]> > >>> http://tp.its.yale.edu/mailman/listinfo/cas-dev > >>> > >>> > >>> -- > >>> Andrew Feller, Analyst > >>> LSU University Information Services > >>> 200 Frey Computing Services Center > >>> Baton Rouge, LA 70803 > >>> Office: 225.578.3737 > >>> Fax: 225.578.6400 > >>> > >>> _______________________________________________ > >>> cas-dev mailing list > >>> [email protected] <mailto:[email protected]> > >>> http://tp.its.yale.edu/mailman/listinfo/cas-dev > >>> > >>> > >>> > ------------------------------------------------------------------------ > >>> > >>> _______________________________________________ > >>> cas-dev mailing list > >>> [email protected] > >>> http://tp.its.yale.edu/mailman/listinfo/cas-dev > >>> > >>> > >> _______________________________________________ > >> cas-dev mailing list > >> [email protected] > >> http://tp.its.yale.edu/mailman/listinfo/cas-dev > >> > > > > > > _______________________________________________ > cas-dev mailing list > [email protected] > http://tp.its.yale.edu/mailman/listinfo/cas-dev >
_______________________________________________ cas-dev mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas-dev
