If my memory serves me well one of the issues with plugins is missing classloading isolation. If you have two plugins installed on a single node they can clash (we have been hit by this with our own plugins and it took us some time to figure it out because the symptom was not deterministic). If Marvel contains Java code that is installed as a plugin it would be imo useful if the code were a bit more transparent, especially for plugin developers.
Regards, Lukáš On Wed, Jan 29, 2014 at 2:42 AM, Ivan Brusic <i...@brusic.com> wrote: > Marvel doesn't different much from elasticsearch plugins in that the code > now runs in the same JVM instead of a separate process. The event data is > pushed rather than pulled. It is great not having to re-invent the wheel, > but having monitoring outside of elasticsearch is not an issue. Great > observation about the tribe node BTW. > > Given that efficient JSON parsing libraries exist in most languages, I > rather go that route over the cat API. Time to re-visit monitoring. > > Ivan > > > On Tue, Jan 28, 2014 at 5:33 PM, Mark Walkom <ma...@campaignmonitor.com>wrote: > >> Or perhaps something could come from the new cat API if they don't want >> to go that route. >> >> Regards, >> Mark Walkom >> >> Infrastructure Engineer >> Campaign Monitor >> email: ma...@campaignmonitor.com >> web: www.campaignmonitor.com >> >> >> On 29 January 2014 12:21, joergpra...@gmail.com <joergpra...@gmail.com>wrote: >> >>> Marvel comes with hidden Java plugin code for an event pusher. Node >>> events, route events, and shard events of ES can be indexed into ES. Very >>> useful for historic analysis and post mortem views. >>> >>> It seems this was also a motivation for the tribe node mode: grow two >>> separate clusters, one for the data, another one for the metrics. >>> >>> It would be nice if also the event pushing source code could be opened, >>> so other monitoring tools are able to build on this facility too. Or at >>> least documenting the event pushing API, for re-implementing it from >>> scratch. >>> >>> Jörg >>> >>> -- >>> 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 elasticsearch+unsubscr...@googlegroups.com. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/elasticsearch/CAKdsXoG-JaWZU4qFQsUaM_UHCwkzMdYnLruUHNmcnkiZ-wX6jA%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 elasticsearch+unsubscr...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/elasticsearch/CAEM624Yn5y1bxGYd%3DjeG%3DiUVzowhOsuzKi_8erKrPEmTNbxb%3DQ%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 elasticsearch+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/elasticsearch/CALY%3DcQD%3Dh804DJBr2J8V3gDvkSK0ddXHvg0xDBf9XYzUza_n5w%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 elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAO9cvUbtaLcYfteU3CO8EWL4oP36OR86cE4Rj-JFEs3SLvjWGA%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
