# Configure an index pattern

In order to use Kibana you must configure at least one index pattern. Index patterns are used to identify the Elasticsearch index to run search and analytics against. They are also used to configure fields.

Index pattern advanced options

{{controller.timeFieldOptionsError}}

Patterns allow you to define dynamic index names using * as a wildcard. Example: logstash-*

Patterns allow you to define dynamic index names. Static text in an index name is denoted using brackets. Example: [logstash-]YYYY.MM.DD. Please note that weeks are setup to use ISO weeks which start on Monday. — Date Format Documentation

Note: I noticed you are using weekly indices. Kibana requires ISO weeks be used in your index creation. See Wikipedia: ISO Week Date

Index pattern ID

Creates the index pattern with the specified ID.

Time Filter field name refresh fields
Expand index pattern when searching [DEPRECATED]

With this option selected, searches against any time-based index pattern that contains a wildcard will automatically be expanded to query only the indices that contain data within the currently selected time range.

Searching against the index pattern logstash-* will actually query Elasticsearch for the specific matching indices (e.g. logstash-2015.12.21) that fall within the current time range.

With recent changes to Elasticsearch, this option should no longer be necessary and will likely be removed in future versions of Kibana.

Use event times to create index names [DEPRECATED]
Time-interval based index patterns are deprecated!
We strongly recommend using wildcard pattern names instead of time-interval based index patterns.
Index pattern interval
{{err}}
Attempted to match the following indices and aliases:
{{sample}}
Pattern matches {{controller.existing.matchPercent}} of existing indices and aliases
{{match}}
Indices and aliases that were found, but did not match the pattern:
{{match}}
more