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+unsubscr...@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.
