Open nreese opened 3 months ago
Pinging @elastic/kibana-presentation (Team:Presentation)
Feed back from Elasticsearch team
"The reason is quite simple: ES is not a proxy. These requests can rather easily be sent to remote clusters directly. Otherwise we need to have cross cluster support for all our API. We document which API support this explicitly"
Use the resolve index API to get cluster connection information and and then call get index settings directly for the remote cluster.
Steps to view problem
yarn es snapshot -E transport.port=9500 -E http.port=9201 -E path.data=../remote1
elasticsearch.hosts: ["http://localhost:9201"]
to kibana.dev.yml. Note createconfig/kibana.dev.yml
if one does not exist. kibana.dev.yml is not managed by git so it has to be created the first time you add values.yarn start
to start kibana processelasticsearch.hosts
from kibana.dev.ymlyarn es snapshot -E path.data=../local1
remote1:kibana_sample_data_logs
remote1:kibana_sample_data_logs
data view. Notice warning about index settings read failureGET /remote1:kibana_sample_data_logs/_settings
in console and get same error.Elasticsearch get index settings API does not support remote index. We will need to investigate how to get
max_result_window
from remote index.