Forum Discussion

Brandon's avatar
Brandon
8 years ago

Apache 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 datasources use 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">

solr
  • Brandon's avatar
    Brandon
    7 years ago

    @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!

    /topic/1887-solr-error-logs/

     

  • George_Bica's avatar
    George_Bica
    7 years ago

    @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.