Hi, we're developing an OS ES security plugin (https://github.com/floragunncom/search-guard) and are interested in this as well. From your explanation, it seems that Graylog connects to ES the same way as tribe nodes do (tribe nodes also open non-data, non-master nodes for each cluster they talk to). We're just about to release tribe support, and for it to work, we also had to add our own plugins to the embedded client nodes. So I'm just wondering what exact problems you run into. Is there anything we can help you with regarding this functionality?
Thanks, Jochen Am Mittwoch, 6. Juli 2016 11:53:33 UTC+2 schrieb Jochen Schalanda: > > Hi Rennie, > > Graylog currently hosts an embedded Elasticsearch instance which joins the > Elasticsearch cluster as a client node (i. e. no data is stored and it's > not master-eligible). Due to some kind of "sanity check" (the JarHell > check), the embedded Elasticsearch node fails to load any plugins in this > mode. > > There's currently no workaround for this and will need some extensive > changes in Graylog to make it work, so don't hold your breath. > > Cheers, > Jochen > > On Wednesday, 6 July 2016 09:58:09 UTC+2, Ano nym wrote: >> >> Am Mittwoch, 6. Juli 2016 09:54:25 UTC+2 schrieb Jan Doberstein: >>> >>> this will not be solved in the next weeks. Just because of some >>> technical reasons. >>> >> >> Hi Jan, >> >> did you´ve some details to the "technical reasons"? We may be able to >> support you? >> >> Kind regards, >> >> Rennie >> > -- You received this message because you are subscribed to the Google Groups "Graylog Users" 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/graylog2/2b6c0a25-1f52-4f9f-8700-a906ad9e3de7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
