[docs] Link to client api, move client library docs to core development section

This commit is contained in:
Jonathan Budzenski 2017-01-11 14:27:56 -06:00
parent 92ee7e12a5
commit deafe5a435
No known key found for this signature in database
GPG key ID: D28BF9418FA0F292
3 changed files with 4 additions and 4 deletions

View file

@ -10,3 +10,5 @@ include::core/development-basepath.asciidoc[]
include::core/development-dependencies.asciidoc[]
include::core/development-modules.asciidoc[]
include::plugin/development-elasticsearch.asciidoc[]

View file

@ -14,5 +14,3 @@ The Kibana plugin interfaces are in a state of constant development. We cannot
include::plugin/development-plugin-resources.asciidoc[]
include::plugin/development-uiexports.asciidoc[]
include::plugin/development-elasticsearch.asciidoc[]

View file

@ -3,7 +3,7 @@
Kibana exposes two clients on the server and browser for communicating with elasticsearch.
There is an 'admin' client which is used for managing Kibana's state, and a 'data' client for all
other requests. The clients use the elasticsearch.js library.
other requests. The clients use the https://www.elastic.co/guide/en/elasticsearch/client/javascript-api/current/index.html[elasticsearch.js library].
[float]
[[client-server]]
@ -35,7 +35,7 @@ uiModules.get('kibana')
es.ping()
.then(() => esAdmin.ping())
.catch(err => {
console.log('error pinging servers);
console.log('error pinging servers');
});
});
----