Hi Justin Thanks for inputs.
Regards. justinedelson wrote: > > Threads are the responsibility of the JVM. They're monitorable via JMX > on modern VMs. > > Diskspace is the responsibility of the OS. I don't know what OS you're > running so I can't tell you how to monitor this, but presumably there's > a way to do it. > > Number of documents in terms of size seems like something specific to > your application, so you should write your own monitoring (JMX MBean?) > for this. > > Justin > > On 3/5/11 3:37 AM, abk wrote: >> Hi Alex/Memebrs, >> >> Any suggestion ? >> >> Regards. >> >> >> abk wrote: >>> >>> Hi Alex, >>> Thanks for reply. >>> >>> By monitoring I mean general repository health check kind of thing. For >>> example number of document in terms of size, Disk Space, Running Threads >>> etc or anything else related. >>> So that user can view it through web interface just like in tomcat we >>> have >>> status interface http://localhost:8080/manager/status >>> >>> Regards. >>> >>> >>> >>> Alexander Klimetschek-2 wrote: >>>> >>>> On 04.03.11 11:34, "abk" wrote: >>>>> What type of monitoring is available in JackRabbit. Or anyother API we >>>>> have >>>>> to use for monitoring. >>>> >>>> What kind of monitoring do you mean? If the server / repo is up and >>>> running (this is more left to the servlet container, I think)? Or >>>> content >>>> change monitoring? For this, JCR observations are great. >>>> >>>> Regards, >>>> Alex >>>> >>>> -- >>>> Alexander Klimetschek >>>> Developer // Adobe (Day) // Berlin - Basel >>>> >>> >> >> >> -- >> View this message in context: >> http://jackrabbit.510166.n4.nabble.com/Monitoring-in-JackRabbit-tp3335003p3336404.html >> Sent from the Jackrabbit - Dev mailing list archive at Nabble.com. > -- View this message in context: http://jackrabbit.510166.n4.nabble.com/Monitoring-in-JackRabbit-tp3335003p3336794.html Sent from the Jackrabbit - Dev mailing list archive at Nabble.com.
