SOLR JVM Stats (non-JMX)
ANLX64 This monitors solr JVM stats via the SOLR API without the need to enable jmx. This datasource may not work on older solr versions as this particular API call was only recently introduced. Still, it should be very useful for monitoring the overall health of the JVM application.1View0likes7CommentsSolr Collection Statistics (non-JMX)
3Z32Z4 This datasource monitors a large amount of SOLR performance data for each SOLR collection/core. It is done via batchscript and appears to return data extremely reliably and efficiently. There are no alert thresholds set up as performance expectations may vary depending on usage. I've also set up basic overview and per-instance graphs. There are 65 datapoints here though, so I'm sure more can be added.0Views0likes2CommentsSOLR Collection Satus (non-JMX)
ZLPJP3 This datasource monitors the status of each solr collection without the need to enable JMX. It is done via batchscript and seems to be very efficient. The only alert set up is for cores that are recovering. Other alerts can be set up at your discretion. There are a few graphs included as well.0Views0likes1CommentApache Solr datasources need scrubbing
I'm not sure where else to post this, but I wanted to make sure the LogicMonitor team takes another look at the apache solr datasources in the repository as they need to be scrubbed. Currently these datasourcesuse applies to rules that seem to be very specific to one customer. Here is one example: contains(system.groups,"SEARCH/CHI/SLAVE/JOB") or contains(system.groups,"SEARCH/AMS/SLAVE/JOB") or contains(system.groups,"SEARCH/QTW/SLAVE/JOB") or contains(system.groups,"SEARCH/CHI/MASTER/JOB") or contains(system.groups,"SEARCH/AMS/MASTER/JOB") or contains (system.groups,"SEARCH/QTW/SLAVE/JobAux") or contains(system.groups,"SEARCH/CHI/SLAVE/JOBAUX") or system.displayname =~ "solrone" I should also mention that I have completely rebuilt these datasources and combined them into a single datasource that pulls all of this data with a single API query. I'll be submitting it after I scrub and polish it. :)/emoticons/smile@2x.png 2x" title=":)" width="20">0Views1like12CommentsSOLR Error Logs
W9PN3Y I thought I had already posted this one, but regardless - here it is. This does not apply to any servers by default as it can be extremely noisy if you don't have it tuned. This makes an API call to solr to pull error and severe logs and then formats them so that LogicMonitor can understand them. Before applying this, it's not a bad idea to review those logs manually to make sure something isn't repeatedly triggering (as is common with SOLR). Still - it's helped us detect and diagnose a range of issues that would have otherwise been difficult to see.0Views0likes0CommentsSolr Error Logs
This datasource monitors the solr logs via an http call to the web front end and parses the json response to output in aLogicMonitor-friendly format. This appears to work on all of the versions of Solr I have tested on (6.0+). *Note - I have disabled the applies-to on this datasource because it can be quite noisy if your logging hasn't been tuned on the Solr nodes. I did include some useful filters to strip out some of the more common noise - but I still recommend applying this with caution. W9PN3Y1View1like0Comments
