WARNING: Version 6.0 of Kibana has passed its EOL date.
This documentation is no longer being maintained and may be removed. If you are running this version, we strongly advise you to upgrade. For the latest information, see the current release documentation.
Each set of data loaded to Elasticsearch has an index pattern. In the previous section, the
Shakespeare data set has an index named
shakespeare, and the accounts data set has an index named
bank. An index
pattern is a string with optional wildcards that can match multiple indices. For example, in the common logging use
case, a typical index name contains the date in YYYY.MM.DD format, and an index pattern for May would look something
For this tutorial, any pattern that matches the name of an index we’ve loaded will work. Open a browser and
localhost:5601. Click the Management tab, then the Index Patterns tab. Click Add New to define a new index
pattern. Two of the sample data sets, the Shakespeare plays and the financial accounts, don’t contain time-series data.
Make sure the Index contains time-based events box is unchecked when you create index patterns for these data sets.
shakes* as the index pattern for the Shakespeare data set and click Create to define the index pattern, then
define a second index pattern named
The Logstash data set does contain time-series data, so after clicking Add New to define the index for this data
set, make sure the Index contains time-based events box is checked and select the
@timestamp field from the
Time-field name drop-down.
When you define an index pattern, indices that match that pattern must exist in Elasticsearch. Those indices must
contain data. You can check what indices exist by using
GET _cat/indices in Console, under Dev Tools, or
curl -XGET "http://localhost:9200/_cat/indices".