When we migrated from Sense plugin to Console packaged with Kibana in 5.0, the ability to reference a different elasticsearch url for issuing queries from the editor was removed and it is now dependent on the value of elasticsearch.url
in the kibana yml.
This is a breaking change and will be nice to document accordingly.
@debadair
cc @epixa
also is the screenshot wrong within documentation: https://www.elastic.co/guide/en/kibana/current/console-kibana.html, there is no server url field
@tylersmalley mentioned in #10751 :
I am leaning towards leaving this out of the breaking changes doc as it was a plugin prior to 5.x and not in Kibana core.
I loved that I could use the sense plugin to hit different servers. Now, that is gone. The Chrome extension for sense has also been removed. Any chance is this feature will ever be added back? Or any workarounds. I don't imagine restarting Kibana each time with a different configuration.
Having this ability is really useful. Please consider to add this back on the console UI
migrating from one ES version to another is now a bit pain. before i simply used sense as chrome plugin, now i've to setup to different kibana servers to use sense for both.
@tylersmalley Can we close this issue?
@gchaps, this issue is actually still valid. Prior to bringing Console (known as Sense at the time) into Kibana, it allowed for the user to connect to additional ES clusters. This was removed during that migration as it was essentially an open proxy within Kibana.
Pinging @elastic/kibana-docs
Pinging @elastic/es-ui
I'm going to close this because 5.x is EOL at this point, so updating the docs seems moot. I think that allowing Console to send requests to arbitrary ES clusters is interesting, so I opened https://github.com/elastic/kibana/issues/48406 so we can discuss this feature.
Most helpful comment
I loved that I could use the sense plugin to hit different servers. Now, that is gone. The Chrome extension for sense has also been removed. Any chance is this feature will ever be added back? Or any workarounds. I don't imagine restarting Kibana each time with a different configuration.