mirror of
https://github.com/elastic/kibana.git
synced 2025-04-23 17:28:26 -04:00
[tribe] Init docs
This commit is contained in:
parent
e6669ee19d
commit
42e59dbbe8
5 changed files with 37 additions and 8 deletions
|
@ -12,3 +12,5 @@ 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[]
|
|
@ -0,0 +1,4 @@
|
|||
[[development-elasticsearch]]
|
||||
=== Communicating with elasticsearch
|
||||
|
||||
Kibana exposes clients for communicating with elasticsearch on the server passed into each plugin.
|
|
@ -56,6 +56,8 @@ include::setup/access.asciidoc[]
|
|||
|
||||
include::setup/connect-to-elasticsearch.asciidoc[]
|
||||
|
||||
include::setup/tribe.asciidoc[]
|
||||
|
||||
include::setup/production.asciidoc[]
|
||||
|
||||
include::setup/upgrade.asciidoc[]
|
||||
|
|
|
@ -4,7 +4,6 @@
|
|||
* <<configuring-kibana-shield, Using Kibana with X-Pack>>
|
||||
* <<enabling-ssl, Enabling SSL>>
|
||||
* <<load-balancing, Load Balancing Across Multiple Elasticsearch Nodes>>
|
||||
* <<kibana-tribe, Kibana and Tribe Nodes>>
|
||||
|
||||
How you deploy Kibana largely depends on your use case. If you are the only user,
|
||||
you can run Kibana on your local machine and configure it to point to whatever
|
||||
|
@ -112,10 +111,3 @@ cluster.name: "my_cluster"
|
|||
# The Elasticsearch instance to use for all your queries.
|
||||
elasticsearch.url: "http://localhost:9200"
|
||||
--------
|
||||
|
||||
[float]
|
||||
[[kibana-tribe]]
|
||||
=== Kibana and Tribe Nodes
|
||||
|
||||
Kibana 5.0 does not support tribe nodes. We are working on a solution that
|
||||
addresses this limitation.
|
||||
|
|
29
docs/setup/tribe.asciidoc
Normal file
29
docs/setup/tribe.asciidoc
Normal file
|
@ -0,0 +1,29 @@
|
|||
[[tribe]]
|
||||
== Using Kibana with Tribe nodes
|
||||
|
||||
Kibana can be configured to connect to a tribe node for data retrieval. Because tribe nodes can't create indices, Kibana additionally
|
||||
requires a separate connection to a node to maintain state. When configured, searches and visualizations will retrieve data using
|
||||
the tribe node and administrative actions (such as saving a dashboard) will be sent to non-tribe node.
|
||||
|
||||
[float]
|
||||
[[tribe-configuration]]
|
||||
=== Configuring Kibana for tribe nodes
|
||||
|
||||
Tribe nodes take all of the same configuration options used when configuring elasticsearch in `kibana.yml`. Tribe options
|
||||
are prefixed with `elasticsearch.tribe` and at a minimum requires a url:
|
||||
[source,text]
|
||||
----
|
||||
elasticsearch.url: "<your_administration_node>"
|
||||
elasticsearch.tribe.url: "<your_tribe_node>"
|
||||
----
|
||||
|
||||
The full list of configurations can be found at <<settings>>.
|
||||
|
||||
[float]
|
||||
[[tribe-limitations]]
|
||||
=== Limitations
|
||||
|
||||
Due to the ambiguity of which cluster is being used, certain features are disabled in Kibana:
|
||||
|
||||
* Console
|
||||
* Managing users and roles with the x-pack plugin
|
Loading…
Add table
Add a link
Reference in a new issue