github-mirrors/kibana
1
0
Fork 0
mirror of https://github.com/elastic/kibana.git synced 2025-04-23 17:28:26 -04:00
Code Issues Projects Releases Packages Wiki Activity

Updated from review comments, re-commented-out repository part for master

Browse source
This commit is contained in:
LeeDr 2016-07-25 10:52:16 -05:00
parent 32ed1ceb4d
commit 50d540df4c
2 changed files with 18 additions and 18 deletions
Download patch file Download diff file Expand all files Collapse all files

2
docs/kibana-repositories.asciidoc
View file

@ -1,5 +1,5 @@
[[setup-repositories]]
=== Kibana Repositories
=== Install Kibana using a Linux Package Manager
Binary packages for Kibana are available for Unix distributions that support the `apt` and `yum` tools. We also have
repositories available for APT and YUM based distributions.

34
docs/setup.asciidoc
View file

@ -18,39 +18,39 @@ Your existing Kibana version is generally compatible with the next minor version
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.
. https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-snapshots.html[snapshot] existing `.kibana` index in Elasticsearch
. save a backup copy of the existing `config/kibana.yml`
. take note of the Kibana plugins that are installed;
.. `/opt/kibana/bin/kibana plugin --list` on 4.x versions of Kibana.
.. `/usr/share/kibana/bin/kibana-plugin --list` on 5.x versions of Kibana.
. For Kibana installations using an extracted **archive file**;
.. 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
. For Kibana installations using a Linux **package manager**;
.. uninstall the existing Kibana package `apt-get remove kibana` or `yum remove kibana`
.. install the new Kibana package. See steps below. (There have been some installer issues between various version of Kibana so the uninstall and install process is safer than an upgrade.)
. 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.
. 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:
.. 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:
.. Uninstall the existing Kibana package `apt-get remove kibana` or `yum remove kibana`
.. Install the new Kibana package. See steps below. (There have been some installer issues between various version of Kibana so the uninstall and install process is safer than an upgrade.)
[float]
[[install]]
=== Install and Start Kibana from archive file
=== Install and Start Kibana from Archive File
To get Kibana up and running:
. Download the https://www.elastic.co/downloads/kibana[Kibana {version} binary package] for your platform.
. Extract the `.zip` or `tar.gz` archive file.
. If upgrading, copy configuration changes from the previous kibana.yml to the new version.
. Optionally install Kibana plugins.
. Install Kibana plugins (optional).
. Run Kibana from the install directory: `bin/kibana` (Linux/MacOSX) or `bin\kibana.bat` (Windows).
On Unix, you can instead run the package manager suited for your distribution.
////
[float]
include::kibana-repositories.asciidoc[]
////
That's it! Kibana is now running on port 5601.