Otis, Unfortunately introducing a new third party app isn't an option for me though I can understand your bias toward SPM. I agree that extending a RHB for monitoring doesn't feel right which is why I was asking for a better place to put it, as part of a suggestion that I submit a patch from solr-user. An unapplied patch on a jira issue is better than no patch at all, right?
Thanks, Greg On Mon, Feb 3, 2014 at 10:06 PM, Otis Gospodnetic < otis.gospodne...@gmail.com> wrote: > Hi Greg, > > This sounds overly complex to me. Extending a RHB to aid you in > monitoring doesn't feel right. Have you considered using monitoring tools > that can provide you with aggregated views and such? Have a look at > http://sematext.com/spm , which can do that for you and much more without > you having to hack Solr. > > Otis > -- > Performance Monitoring * Log Analytics * Search Analytics > Solr & Elasticsearch Support * http://sematext.com/ > > > On Mon, Feb 3, 2014 at 3:19 PM, Greg W <allrightn...@gmail.com> wrote: > >> I've written a custom mbean that aggregates data from all the >> RequestHandler mbeans in a jvm to provide aggregate statistics for easier >> monitoring and currently I'm ensuring it gets ran by actually extending >> RequestHandlerBase and including the class as a request handler in >> solrconfig.xml. I don't think this is the ideal way of getting this code to >> run but as a quick hack it got the job done. If I wanted to ensure this >> class ran / register the mbean at a more appropriate place, earlier on in >> solr's initialization, where would that be? >> >> Thanks, >> Greg >> > >
