From 22aa46e8501790f0da0bdac9d358ad8e6ac7e041 Mon Sep 17 00:00:00 2001 From: Natalie Date: Fri, 11 May 2018 01:35:53 +0200 Subject: [PATCH] Update `Defining Your Index Patterns` page (#14117) * Update define index tutorial * Rename Create->Next step --- docs/getting-started/tutorial-define-index.asciidoc | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/docs/getting-started/tutorial-define-index.asciidoc b/docs/getting-started/tutorial-define-index.asciidoc index df84b2fc25e6..e737fa901585 100644 --- a/docs/getting-started/tutorial-define-index.asciidoc +++ b/docs/getting-started/tutorial-define-index.asciidoc @@ -8,10 +8,7 @@ case, a typical index name contains the date in YYYY.MM.DD format, and an index like `logstash-2015.05*`. For this tutorial, any pattern that matches the name of an index we've loaded will work. Open a browser and -navigate to `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. -Specify `shakes*` as the index pattern for the Shakespeare data set and click *Create* to define the index pattern, then +navigate to `localhost:5601`. Click the *Management* tab, then the *Index Patterns* tab. Under *Index Pattern* specify `shakes*` as the index pattern for the Shakespeare data set and click *Next step* to define the index pattern, then define a second index pattern named `ba*`. The Logstash data set does contain time-series data, so after clicking *Add New* to define the index for this data