Merge branch '4.3docs' into 4.3

This commit is contained in:
Paul Echeverri 2015-11-24 08:22:55 -08:00
commit 89ca5f5b35
6 changed files with 15 additions and 25 deletions

View file

@ -6,15 +6,14 @@ When a refresh interval is set, it is displayed to the left of the Time Filter i
To set the refresh interval:
. Click the *Time Filter* image:images/TimeFilter.jpg[Time
Filter] in the upper right corner of the menu bar.
. Click the *Time Filter* image:images/TimeFilter.jpg[Time Filter] in the upper right corner of the menu bar.
. Click the *Refresh Interval* tab.
. Choose a refresh interval from the list.
To automatically refresh the data, click the image:images/autorefresh.png[] *Auto-refresh* button and select an
autorefresh interval:
image::images/autorefresh-intervals.png
image::images/autorefresh-intervals.png[]
When auto-refresh is enabled, Kibana's top bar displays a pause button and the auto-refresh interval:
image:images/autorefresh-pause.png[]. Click the *Pause* button to pause auto-refresh.

View file

@ -13,10 +13,8 @@ dashboards that display changes to Elasticsearch queries in real time.
Setting up Kibana is a snap. You can install Kibana and start exploring your
Elasticsearch indices in minutes -- no code, no additional infrastructure required.
NOTE: This guide describes how to use Kibana 4.2. For information about what's new
in Kibana 4.2, see the <<releasenotes, release notes>>. For earlier versions of Kibana 4, see the
http://www.elastic.co/guide/en/kibana/4.1/index.html[Kibana 4.1 User Guide]. For information about Kibana 3, see the
http://www.elastic.co/guide/en/kibana/3.0/index.html[Kibana 3 User Guide].
NOTE: This guide describes how to use Kibana 4.3. For information about what's new
in Kibana 4.3, see the <<releasenotes, release notes>>.
[float]
[[data-discovery]]

View file

@ -121,6 +121,7 @@ path to that configuration file each time you use the `bin/kibana plugin` comman
74:: I/O error
70:: Other error
[float]
[[plugin-switcher]]
== Switching Plugin Functionality

View file

@ -3,9 +3,9 @@
The 4.3 release of Kibana requires Elasticsearch 2.1 or later.
Time-based index patterns are *deprecated* in this release of Kibana. Support for time-based index patterns will be removed
entirely in the next major Kibana release. Elasticsearch 2.0 includes sophisticated date parsing APIs that Kibana uses to
determine date information, removing the need to specify dates in the index pattern name.
Using event times to create index names is *deprecated* in this release of Kibana. Support for this functionality will be
removed entirely in the next major Kibana release. Elasticsearch 2.1 includes sophisticated date parsing APIs that Kibana
uses to determine date information, removing the need to specify dates in the index pattern name.
[float]
[[enhancements]]

View file

@ -35,19 +35,11 @@ list.
contains time-based events* option and select the index field that contains the timestamp. Kibana reads the index
mapping to list all of the fields that contain a timestamp.
. If new indices are generated periodically and have a timestamp appended to the name, select the *Use event times to
create index names* option and select the *Index pattern interval*. This enables Kibana to search only those indices
that could possibly contain data in the time range you specify. This is primarily applicable if you are using Logstash
to feed data into Elasticsearch.
. Click *Create* to add the index pattern.
. To designate the new pattern as the default pattern to load when you view the Discover tab, click the *favorite*
button.
NOTE: Using event times in index names is deprecated in the 4.3 release of Kibana. Kibana and Elasticsearch can now
parse index names with timestamp information automatically.
To use an event time in an index name, enclose the static text in the pattern and specify the date format using the
tokens described in the following table.
@ -267,6 +259,8 @@ To set advanced options:
. Enter a new value for the option.
. Click the *Save* button.
include::advanced-settings.asciidoc[]
[[kibana-server-properties]]
=== Setting Kibana Server Properties

View file

@ -76,18 +76,16 @@ image:images/Start-Page.png[Kibana start page]
. Specify an index pattern that matches the name of one or more of your Elasticsearch indices. By default, Kibana
guesses that you're working with data being fed into Elasticsearch by Logstash. If that's the case, you can use the
default `logstash-*` as your index pattern. The asterisk (*) matches zero or more characters in an index's name. If
your Elasticsearch indices follow some other naming convention, enter an appropriate pattern. The "pattern" can also
your Elasticsearch indices follow some other naming convention, enter an appropriate pattern. The "pattern" can also
simply be the name of a single index.
. Select the index field that contains the timestamp that you want to use to perform time-based comparisons. Kibana
reads the index mapping to list all of the fields that contain a timestamp. If your index doesn't have time-based data,
disable the *Index contains time-based events* option.
WARNING: Time-based index patterns are *deprecated* in this release of Kibana. Support for time-based index patterns will
be removed entirely in the next major Kibana release. Elasticsearch 2.0 includes sophisticated date parsing APIs that
+
WARNING: Using event times to create index names is *deprecated* in this release of Kibana. Support for this functionality
will be removed entirely in the next major Kibana release. Elasticsearch 2.1 includes sophisticated date parsing APIs that
Kibana uses to determine date information, removing the need to specify dates in the index pattern name.
. If new indices are generated periodically and have a timestamp appended to the name, select the *Use event times to
create index names* option and select the *Index pattern interval*. This improves search performance by enabling Kibana
to search only those indices that could contain data in the time range you specify. This is primarily applicable if you
are using Logstash to feed data into Elasticsearch.
+
. Click *Create* to add the index pattern. This first pattern is automatically configured as the default.
When you have more than one index pattern, you can designate which one to use as the default from *Settings > Indices*.