Solr does have a monitoring wiki page, but it is fairly weak and could use more serious contribution, including suggestions from this email thread.
This is also a good example of where the wiki still has value relative to the formal Solr Reference Guide. E.g., third parties can add tool and service descriptions and users can add their experiences and own tips. The Reference Guide probably should have at least a cursory summary of Solr monitoring (beyond just documenting JMX), probably simply referring users to the wiki. IOW, details on monitoring are beyond the scope of the Reference Guide itself (other than raw JMX and ping.) -- Jack Krupansky On Wed, Dec 23, 2015 at 6:27 AM, Emir Arnautovic < emir.arnauto...@sematext.com> wrote: > Hi Shail, > As William mentioned, our SPM <https://sematext.com/spm/index.html> > allows you to monitor all main Solr/Jvm/Host metrics and also set up alerts > for some values or use anomaly detection to notify you when something is > about to be wrong. You can test all features for free for 30 days (no > credit card required). There is embedded chat if you have some questions. > > HTH, > Emir > > -- > Monitoring * Alerting * Anomaly Detection * Centralized Log Management > Solr & Elasticsearch Support * http://sematext.com/ > > > > On 23.12.2015 07:38, William Bell wrote: > >> Sematext.com has a service for this... >> >> Or just curl "http://localhost:8983/solr/<collection>/select?q=*:*" to >> see >> if it returns ? >> >> On Tue, Dec 22, 2015 at 12:15 PM, Tiwari, Shailendra < >> shailendra.tiw...@macmillan.com> wrote: >> >> Hi, >>> >>> Last week our Solr Search was un-responsive and we need to re-boot the >>> server, but we were able to find out after customer complained about it. >>> What's best way to monitor that search is working? >>> We can always add Gomez alerts from UI. >>> What are the best practices? >>> >>> Thanks >>> >>> Shail >>> >> >> >> >> >
