kibana/docs/setup.asciidoc

132 lines
6.5 KiB
Plaintext
Raw Normal View History

[[setup]]
2016-07-22 20:25:11 +02:00
== Installing Kibana
You can set up Kibana and start exploring your Elasticsearch indices in minutes.
2015-01-23 23:37:26 +01:00
All you need is:
2016-04-02 20:36:04 +02:00
* Elasticsearch {esversion}
2016-07-22 20:25:11 +02:00
* A modern web browser - https://www.elastic.co/support/matrix#show_browsers[Supported Browsers].
* Information about your Elasticsearch installation:
** URL of the Elasticsearch instance you want to connect to.
** Which Elasticsearch indices you want to search.
2015-02-17 21:06:32 +01:00
NOTE: If your Elasticsearch installation is protected by http://www.elastic.co/overview/shield/[{scyld}], see
{shield}/kibana.html#using-kibana4-with-shield[{scyld} with Kibana] for additional setup instructions.
2015-01-23 23:37:26 +01:00
2016-07-22 20:25:11 +02:00
=== Upgrading Kibana
Your existing Kibana version is generally compatible with the next minor version release of Elasticsearch.
This means you should upgrade your Elasticsearch cluster(s) before or at the same time as Kibana.
We cannot guarantee compatibility between major version releases so in those cases both Elasticsearch and Kibana must be upgraded together.
2016-08-03 18:27:32 +02:00
To upgrade Kibana:
2016-07-29 15:40:39 +02:00
. Create a https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-snapshots.html[snapshot] of the existing `.kibana` index.
. Back up the `kibana.yml` configuration file.
2016-07-29 15:40:39 +02:00
. Take note of the Kibana plugins that are installed:
* `bin/kibana plugin --list` on 4.x versions of Kibana.
* `bin/kibana-plugin list` on 5.x versions of Kibana.
. To upgrade from an Archive File:
2016-08-03 18:27:32 +02:00
.. Extract the new version of Kibana into a different directory. See steps below.
.. Migrate any custom configuration from your old kibana.yml to your new one
.. Follow other steps below to complete the new installation.
.. Once the new version is fully configured and working with required plugins, remove the previous version of Kibana
. To upgrade using a Linux Package Manager:
2016-08-03 18:27:32 +02:00
.. Uninstall the existing Kibana package: `apt-get remove kibana` or `yum remove kibana`
.. Install the new Kibana package. There have been some installer issues between various version of Kibana so the uninstall and install process is safer than an upgrade.
2016-07-22 20:25:11 +02:00
2015-02-14 20:20:30 +01:00
[float]
[[install]]
2016-07-29 15:40:39 +02:00
=== Install and Start Kibana from an Archive File
2015-01-23 23:37:26 +01:00
To get Kibana up and running:
. Download the https://www.elastic.co/downloads/kibana[Kibana {version} binary package] for your platform.
2015-01-23 23:37:26 +01:00
. Extract the `.zip` or `tar.gz` archive file.
2016-08-03 18:27:32 +02:00
. If you're upgrading, migrate any configuration changes from the previous `kibana.yml` to the new version.
. Install Kibana plugins (optional).
2016-07-22 20:25:11 +02:00
. Run Kibana from the install directory: `bin/kibana` (Linux/MacOSX) or `bin\kibana.bat` (Windows).
2016-04-02 20:36:04 +02:00
On Unix, you can instead run the package manager suited for your distribution.
////
2016-04-02 20:36:04 +02:00
[float]
include::kibana-repositories.asciidoc[]
////
2015-01-23 23:37:26 +01:00
That's it! Kibana is now running on port 5601.
[float]
[[kibana-dynamic-mapping]]
==== Kibana and Elasticsearch Dynamic Mapping
By default, Elasticsearch enables {ref}dynamic-mapping.html[dynamic mapping] for fields. Kibana needs dynamic mapping
2015-06-10 21:58:29 +02:00
to use fields in visualizations correctly, as well as to manage the `.kibana` index where saved searches,
visualizations, and dashboards are stored.
2015-06-10 21:58:29 +02:00
If your Elasticsearch use case requires you to disable dynamic mapping, you need to manually provide mappings for
fields that Kibana uses to create visualizations. You also need to manually enable dynamic mapping for the `.kibana`
index.
The following procedure assumes that the `.kibana` index does not already exist in Elasticsearch and that the
`index.mapper.dynamic` setting in `elasticsearch.yml` is set to `false`:
. Start Elasticsearch.
. Create the `.kibana` index with dynamic mapping enabled just for that index:
+
[source,shell]
PUT .kibana
{
"index.mapper.dynamic": true
}
+
. Start Kibana and navigate to the web UI and verify that there are no error messages related to dynamic mapping.
2015-02-14 20:20:30 +01:00
[float]
[[connect]]
=== Connect Kibana with Elasticsearch
2015-06-10 21:58:29 +02:00
Before you can start using Kibana, you need to tell it which Elasticsearch indices you want to explore. The first time
you access Kibana, you are prompted to define an _index pattern_ that matches the name of one or more of your indices.
That's it. That's all you need to configure to start using Kibana. You can add index patterns at any time from the
<<settings-create-pattern,Settings tab>>.
2015-01-23 23:37:26 +01:00
2015-06-10 21:58:29 +02:00
TIP: By default, Kibana connects to the Elasticsearch instance running on `localhost`. To connect to a different
Elasticsearch instance, modify the Elasticsearch URL in the `kibana.yml` configuration file and restart Kibana. For
information about using Kibana with your production nodes, see <<production>>.
2015-01-23 23:37:26 +01:00
2015-02-18 21:24:06 +01:00
To configure the Elasticsearch indices you want to access with Kibana:
2015-01-23 23:37:26 +01:00
. Point your browser at port 5601 to access the Kibana UI. For example, `localhost:5601` or `http://YOURDOMAIN.com:5601`.
2015-02-14 20:20:30 +01:00
+
2015-11-24 17:25:14 +01:00
image:images/Start-Page.png[Kibana start page]
2015-02-14 20:20:30 +01:00
+
2015-06-10 21:58:29 +02:00
. 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
2015-11-24 17:25:14 +01:00
your Elasticsearch indices follow some other naming convention, enter an appropriate pattern. The "pattern" can also
simply be the name of a single index.
2015-06-10 21:58:29 +02:00
. 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.
2015-11-24 17:25:14 +01:00
+
WARNING: Using event times to create index names is *deprecated* in this release of Kibana. Starting in the 2.1
release, Elasticsearch includes sophisticated date parsing APIs that Kibana uses to determine date information,
removing the need to specify dates in the index pattern name.
2015-11-24 17:25:14 +01:00
+
2015-06-10 21:58:29 +02:00
. 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*.
2015-01-23 23:37:26 +01:00
2016-04-02 20:36:04 +02:00
All done! Kibana is now connected to your Elasticsearch data. Kibana displays a read-only list of fields configured for
the matching index.
2015-01-23 23:37:26 +01:00
2015-02-14 20:20:30 +01:00
[float]
[[explore]]
2015-01-23 23:37:26 +01:00
=== Start Exploring your Data!
You're ready to dive in to your data:
* Search and browse your data interactively from the <<discover, Discover>> page.
* Chart and map your data from the <<visualize, Visualize>> page.
* Create and view custom dashboards from the <<dashboard, Dashboard>> page.
2016-04-02 20:36:04 +02:00
For a tutorial that explores these core Kibana concepts, take a look at the <<getting-started, Getting
Started>> page.