Hi Alex, Yep. I think Jorg (or someone in this thread) suggested this approach. It's likely the approach I will be taking at first swing with the hope of moving later to a hybrid, where the the same core code can be used to install as either a plugin or standalone/separated process running in a different jvm.
On Monday, January 27, 2014 4:13:32 AM UTC-5, Alexander Reelsen wrote: > > Hey Roy, > > another simple solution might be to simply have the plugin run every n > seconds/minutes and check if the node it runs on is currently the master > node. This ensure, that data is collected only on one node in your cluster > and it works in case of outages after the master node reelection... of > course you have dedicated master nodes and those never fail :-) > > In summary, it still might be a better idea to have an external process, > which can be upgraded anytime, even without a cluster outage or another > rolling upgrade. > > > --Alex > > > On Thu, Jan 23, 2014 at 5:14 PM, Ivan Brusic <[email protected]<javascript:> > > wrote: > >> There have been various discussion over the years regarding monitoring. I >> use graphite, but the elasticsearch team also built an a similar service >> with an elasticsearch backend: >> https://github.com/elasticsearch/elasticsearch-metrics-reporter-java. >> >> Of course, this would just gather the data, with no reporting >> capabilities. >> >> Ivan >> >> >> On Wed, Jan 22, 2014 at 9:54 AM, Roy Russo <[email protected]<javascript:> >> > wrote: >> >>> Lukas, >>> >>> Yes, very similar approach in tech, but different in distribution model. >>> The use of RRD makes sense for them, as I believe their offering monitors >>> more than just ES clusters. It's a New Relic type of model. Alternatively, >>> New Relic has ES monitoring plugins available as well. >>> >>> >>> On Wednesday, January 22, 2014 12:00:11 PM UTC-5, Lukáš Vlček wrote: >>>> >>>> Roy, >>>> >>>> Sounds a bit like similar approach to Sematext SPM to me (except they >>>> use CollectD - which is based on RRD is I am not mistaken) - but that >>>> shouldn't stop you. >>>> >>>> As for RHQ it is upstream for JON (JBossON). See >>>> http://planet.jboss.org/post/jboss_operations_network_ >>>> jbosson_jon_rhq_whats_in_a_name >>>> I think it might have been renamed (this happens in JBoss world :-)). >>>> >>>> Regards, >>>> Lukáš >>>> >>>> -- >>> You received this message because you are subscribed to the Google >>> Groups "elasticsearch" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected] <javascript:>. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/elasticsearch/a07a40ac-e1fa-4554-834f-6ab8a268ec24%40googlegroups.com >>> . >>> >>> For more options, visit https://groups.google.com/groups/opt_out. >>> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "elasticsearch" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/elasticsearch/CALY%3DcQDF-G7%2BqYDK5cK5DxZgK6c5NMGwTFDRk%3Dowbi9we8A6Uw%40mail.gmail.com >> . >> >> For more options, visit https://groups.google.com/groups/opt_out. >> > > -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/d3ce9dc9-d5a3-45f8-bed5-c2d511d84379%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
