mirror of
https://github.com/elastic/kibana.git
synced 2025-04-24 01:38:56 -04:00
Revert "[DOCS] Add note about comma syntax in cross cluster search prior to 6.3"
This reverts commit a07cc94459
.
This commit is contained in:
parent
a07cc94459
commit
6f0f6a4645
1 changed files with 4 additions and 3 deletions
|
@ -9,14 +9,15 @@ clusters accordingly. Review the corresponding Elasticsearch
|
|||
{ref}/modules-cross-cluster-search.html[documentation] before attempting to use cross cluster
|
||||
search in Kibana.
|
||||
|
||||
NOTE: Comma notation for cross cluster search is only supported from Kibana 6.3 and onward.
|
||||
If you are running Kibana 6.2 or earlier, use `:test` instead of `cluster_one:test*,cluster_two:test*`.
|
||||
|
||||
Once your Elasticsearch clusters are configured for cross cluster search, you can create
|
||||
specific index patterns in Kibana to search across the clusters of your choosing. Using the
|
||||
same syntax that you'd use in a raw cross cluster search request in Elasticsearch, create your
|
||||
index pattern in Kibana with the convention `<cluster-names>:<pattern>`.
|
||||
|
||||
For example, if you want to query logstash indices across two of the Elasticsearch clusters
|
||||
that you set up for cross cluster search, which were named `cluster_one` and `cluster_two`,
|
||||
you would use `cluster_one:logstash-*,cluster_two:logstash-*` as your index pattern in Kibana.
|
||||
|
||||
Just like in raw search requests in Elasticsearch, you can use wildcards in your cluster names
|
||||
to match any number of clusters, so if you wanted to search logstash indices across any
|
||||
clusters named `cluster_foo`, `cluster_bar`, and so on, you would use `cluster_*:logstash-*`
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue