Logstash altering defined Elasticsearch URL

[Chris_Gatto]

Hello,

I have my Logstash configured with the following output:

output {
    hosts => ["http://myhost/elasticsearch"]
}

This is a valid URL, as I can cURL commands to Elasticsearch with it, such as

curl "http://myhost/elasticsearch/_cat/indices?v"

returns my created indices.

However, when Logstash attempts to create a template, it uses the following URL:

http://myhost/_template/logstash

when I would expect it to use

http://myhost/elasticsearch/_template/logstash

It appears that the /elasticsearch portion of my URL is being chopped off. What's going on here? Is "elasticsearch" a reserved word in the URL that is removed? As far as I can tell, when I issue http://myhost/elasticsearch/elasticsearch, it attempts to find an index named "elasticsearch" which leads me to believe it isn't reserved.

Any help would be greatly appreciated, thanks!

• Chris

EDIT:
I am using Logstash and Elasticsearch 5.0.0

EDIT2:
I have found the following issue:

Unable to fetch mapping because Kibana requests the wrong URL to ES

Hello. I set up Kibana, Logstash and ES using docker-compose. Everything's working fine except that on the "Configure an index pattern" page Kibana can't find the logstash-* indices. I looked at Kibana logs and noticed that it does this: GET /elasticsearch/logstash-*/_mapping/field/*?_=1495837868624&ignore_unavailable=false&allow_no_indices=false&include_defaults=true 404 93ms - 9.0B But gets a 404 because it prefixed the url path with /elasticsearch. However, the indices do exist on this pa…

It seems a similar thing happens when querying Elasticsearch from Kibana; elasticsearch is a Kibana proxy to Elasticsearch. Does this also happen to be the case with Logstash?

EDIT3:

Upon changing the endpoint URL to be

http://myhost/myes

Logstash is still attempting to access

http://myhost/_template/logstash

What might be the problem?

[guyboertje]

Try using the proxy config option.
Or proxy and path
Or hosts and path