Marvel template upload

Elastic Stack Elasticsearch
1

Hi,
I was using marvel in my test environment. As we had authentication
plugin on the REST interface, and noticed the error like:
marvel.agent.exporter ... failed to upload index template, stopping export

I’m pretty sure it’s blocked by the auth plugin, but the question is why
would marvel upload template? If I understand it correctly, the message
comes from java code of marvel. Why the java code choose rest interface
instead of transport interface? Any workaround for the template upload?

Cheers!
Jaguar

--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAP0hgQ2zzzYWb66%3D2QZbmxOajGnKvzaLeKBTf6-%2B81Hso9YSkg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

2

Hi Jaguar,

Marvel requires an index template to make sure some fields get the correct
mappings. Similar in nature to the logstash template
(see https://github.com/logstash-plugins/logstash-output-elasticsearch/blob/master/lib/logstash/outputs/elasticsearch/elasticsearch-template.json
) .

Marvel uses the rest api because the range of ES versions it supports
(0.90.10 -> 1.4.1). Http gives you that flexibility.

Cheers,
Boaz

On Wednesday, November 26, 2014 3:16:03 PM UTC+1, Jaguar wrote:

Hi,
I was using marvel in my test environment. As we had authentication
plugin on the REST interface, and noticed the error like:
marvel.agent.exporter ... failed to upload index template, stopping export

I’m pretty sure it’s blocked by the auth plugin, but the question is why
would marvel upload template? If I understand it correctly, the message
comes from java code of marvel. Why the java code choose rest interface
instead of transport interface? Any workaround for the template upload?

Cheers!
Jaguar

--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/f4cb6670-0d4f-4fcc-ad0e-1eb6fdf827cd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

3

Hi Boaz,
Yes REST interface got less compatibility issue. The only downside for us
is lacking proper authentication header in its REST request. Is there any
plan to support both REST and tranport interface?
Another question, what ’s the version range supported by existing marvel?
If I understand it correctly, Marvel will be loaded into ES process so as
to record some node/cluster wide events via Java API. Those Java API will
evolve over time. I work on the authentication plugin myself l, so such
compatibility issue pop up regularly.

Thanks!
Jaguar

--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAP0hgQ0BhwV_A5R4epjumDcoLRrFnRAWX-fJpu_sj9DyZYaZ1A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

4

Sorry you answered the ersion range question already:)
Thanks!

--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAP0hgQ3Zd%3DWcqnk_MfDaORxhr-0Ka8s%2B06xnaEkm1--%3D65smNQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.