You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-user@lucene.apache.org by "Tiwari, Shailendra" <Sh...@macmillan.com> on 2015/12/22 20:15:33 UTC
Best practices on monitoring Solr
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
Re: Best practices on monitoring Solr
Posted by Modassar Ather <mo...@gmail.com>.
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?
May not be the best way but you can write a class which keeps on checking
the status of all the nodes on SolrCloud (assuming you are using SolrCloud)
on certain interval.
If the node(s) status is down then you can take a decision of restarting
Solr cluster. The restart of SolrCloud can be automated using some script.
If the state of the node(s) is recovering then wait for sometime and check
if it has recovered and has an active state. If it has not recovered even
after some time waiting then take a decision of restarting the SolrCloud
instances.
Hope this helps.
Regards,
Modassar
On Wed, Dec 23, 2015 at 12:45 AM, Tiwari, Shailendra <
Shailendra.Tiwari@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
Re: Best practices on monitoring Solr
Posted by Debraj Manna <su...@gmail.com>.
We use datadog <https://www.datadoghq.com/>.
On Thu, Dec 24, 2015 at 12:44 AM, Ahmet Arslan <io...@yahoo.com.invalid>
wrote:
>
>
> Hi,
>
> http://newrelic.com is another option.
>
> Ahmet
>
> On Wednesday, December 23, 2015 4:26 PM, Florian Gleixner <fl...@redflo.de>
> wrote:
>
>
>
> On 12/22/2015 08:15 PM, Tiwari, Shailendra 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
>
> >
>
>
> Hi,
>
> we are using check_mk to monitor our systems. You can monitor http
> requests with a search query very easily. We also use jolokia (which
> uses jmx) together with the check_mk jolokia plugin to monitor tomcats
> and other java processes - also our zookeeper instances are monitored
> this way. Next on my list is monitoring the solr instances with jolokia.
> I can report here as soon as i have results.
>
> check_mk: http://mathias-kettner.com/check_mk_download.php?LANG=en
> Jolokia: https://jolokia.org/
>
Re: Best practices on monitoring Solr
Posted by Ahmet Arslan <io...@yahoo.com.INVALID>.
Hi,
http://newrelic.com is another option.
Ahmet
On Wednesday, December 23, 2015 4:26 PM, Florian Gleixner <fl...@redflo.de> wrote:
On 12/22/2015 08:15 PM, Tiwari, Shailendra 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
>
Hi,
we are using check_mk to monitor our systems. You can monitor http
requests with a search query very easily. We also use jolokia (which
uses jmx) together with the check_mk jolokia plugin to monitor tomcats
and other java processes - also our zookeeper instances are monitored
this way. Next on my list is monitoring the solr instances with jolokia.
I can report here as soon as i have results.
check_mk: http://mathias-kettner.com/check_mk_download.php?LANG=en
Jolokia: https://jolokia.org/
Re: Best practices on monitoring Solr
Posted by Florian Gleixner <fl...@redflo.de>.
On 12/22/2015 08:15 PM, Tiwari, Shailendra 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
>
Hi,
we are using check_mk to monitor our systems. You can monitor http
requests with a search query very easily. We also use jolokia (which
uses jmx) together with the check_mk jolokia plugin to monitor tomcats
and other java processes - also our zookeeper instances are monitored
this way. Next on my list is monitoring the solr instances with jolokia.
I can report here as soon as i have results.
check_mk: http://mathias-kettner.com/check_mk_download.php?LANG=en
Jolokia: https://jolokia.org/
Re: Best practices on monitoring Solr
Posted by Jack Krupansky <ja...@gmail.com>.
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.arnautovic@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.Tiwari@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
>>>
>>
>>
>>
>>
>
Re: Best practices on monitoring Solr
Posted by Emir Arnautovic <em...@sematext.com>.
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.Tiwari@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
>
>
>
Re: Best practices on monitoring Solr
Posted by William Bell <bi...@gmail.com>.
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.Tiwari@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
--
Bill Bell
billnbell@gmail.com
cell 720-256-8076