Kibana unable to read indexes


#1

Hello, just trying out Kibana 5.3 before upgrading from our 4.6 setup.

We can query at the newly formed indices in devtools and commandline, but Kibana still can't read the indices even though we're using the default format of logstash-*

Filebeat, elasticsearch, logstash, kibana, all at 5.3.0-1. This cluster is on Centos7.


(Mark Walkom) #2

What do you mean by this?


#3

Our indexes are using the format of logstash-%{+YYYY.MM.dd}, same as our previous setup. So figured a the default index of logstash-* would catch it.


#4

Able to query all our indices through devtools or just command line curl commands, but Kibana returns with an unable to fetch mapping error.

Update: we had some old nginx proxy directives in place. Looks like they were interfering with Kibana's ability to grab the data. Below is what we had in place, just commented out the lot of them.

location ~ ^/_plugin/.*$ {
proxy_pass http://127.0.0.1:9200;
proxy_read_timeout 90; }

location ~ ^/_status$ {
proxy_pass http://127.0.0.1:9200;
proxy_read_timeout 90; }

location ~ ^/_cluster/.*$ {
proxy_pass http://127.0.0.1:9200;
proxy_read_timeout 90; }

location ~ ^/_nodes/.*$ {
proxy_pass http://127.0.0.1:9200;
proxy_read_timeout 90; }

location /elasticsearch/ {
proxy_pass http://127.0.0.1:9200/;
proxy_redirect http://127.0.0.1:9200/ /elasticsearch/;
proxy_read_timeout 90; }


(system) #5

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.