Apache Solr datasources need scrubbing

@Brandon Thank you for all these contributions on behalf of all LM community, I will give them a g. We have a lot of SOLR instances and these may prove useful for analytics.

@George Bica - Last one.  This is an eventsource, so no pretty graphs here.  It makes an API call to pull all of the events in the solr log and then alerts on Error and Severe events only.  It doesn't apply to servers by default because it can be quite noisy if you don't have it tuned properly.  Once you're sure it's not going to blow up after you've applied it, go ahead and change the Applies To rules and you should be good to go.  Hope these help!

@Michael Rodrigues - Thanks!  I've got more on the way.

@George Bica - Here's another one.  It might not work for your version of SOLR, but it has the exact same requirements otherwise.  Add solr.port and solr.append to your solr servers and this datasource will provide lots of useful JVM metrics without the need for enabling JMX.

I'm still going through my datasources, so I might still have one or two to post.  I'll keep replying to this thread with whatever I've got.

@Brandon it's been reviewed so it should be importable by all. Thanks for the contribution!

@George Bica

Here's another for monitoring the status of the SOLR collections (as opposed to the performance stats).

@George Bica - I cooked this up and have been steadily improving it over time.  I figured I might as well share it since it seems to be causing you some pain.  :)/emoticons/smile@2x.png 2x" title=":)" width="20">

This datasource polls SOLR via the API and port.  On the device, you'll need to set up these two properties:

• solr.port (default is 8983)
• solr.append (default is solr)

The scripts I put together are pretty efficient, so discovery and monitoring should only take a minute or two to get going.  If it still doesn't work, you might be running into a firewall issue or something.

I've got more SOLR datasources I'll be posting in the next few minutes so keep an eye out.  Though - you might not be able to pull them down until they're cleared by the fine folks at LogicMonitor.

@George Bica the jmx.ports property must be set on the devices manually. The value of the property should be your JMX port(s) separated by commas. Once you've done this, the Apache_SOLR* modules should apply and start collecting. "Solr JVM Stats" has since been deprecated.

JMX was probably selected over the API for expediency, or perhaps that API wasn't around then.

 

We have the following SOLR datasources imported but they are not finding the instances.

• Solr JVM Stats
  • Applies to: solr.port && solr.append
• Apache_SOLR_* (many)
  • applies to: jmx.ports

How do we make the Apache_SOLR_* datasources recognize SOLR instances? They seems to depend on the jmx.ports value, but 8983 is not correct.

This datasource doesn't poll SOLR via the API.  It uses JMX which has to be enabled on your SOLR cores (collections) in solrconfig.xml.  You can read how to do that here:  https://lucene.apache.org/solr/guide/6_6/using-jmx-with-solr.html

JMX provides lots of data that might not be exposed via the standard api queries.  However, SOLR is actually quite good about making sure all sorts of monitoring data is available without JMX and they don't recommend enabling it in production.

5 minutes ago, George Bica said:

Where do we set the jmx.port property, in each device instance?

Where do we set the jmx.port property, in each device instance? and what should the value be? The standard SOLR port is 8983