Go to file
Spencer 4a5ba237df
[6.x] Upgrade to webpack 3 (#14315) (#14824)
* [timelion] remove last remaining amd modules

* [eslint-config-kibana] remove env.amd

* [webpack] use absolute loader names

* [webpack] remove absolute node_modules/ imports

* [webpack] upgrade to webpack 3

* [uiFramework] make webpack build compatible with v3

* [eslint-import-resolver] use https://github.com/elastic/eslint-import-resolver-kibana/pull/21

* [baseOptimizer] don't break when pkg has no dependencies

* [optimize] remove unnecessary json-loader

* [optimize] remove local references to webpack vars

* [eslint] upgrade to eslint-import-resolver-kibana 0.9.0

* [baseOptimizer] comment tweaks

* [baseOptimizer] remove loader pinning

In webpack 1 the loaders defined here were resolved relative to the file they were going to load, which meant that plugins in other projects could accidentally overwrite the loaders Kibana was trying to use, which is why the aliases were used to enforce proper resolution.

In webpack 2 loaders are now resolved relative to the webpackConfig.context, which is set to the root of the Kibana repo. See https://webpack.js.org/configuration/module/#useentry

* [webpack] rely on kibana webpack shims before checking node_modules

(cherry picked from commit f60639fccb)
2017-11-07 15:54:48 -07:00
.github github: PR template checklist in a comment 2017-08-12 10:31:33 -04:00
bin
config Kibana Home page - phase one (#14673) (#14733) 2017-11-02 14:11:24 -06:00
data
docs [6.x] Upgrade to webpack 3 (#14315) (#14824) 2017-11-07 15:54:48 -07:00
maps
packages [flot-charts] move into ui/public (#14669) 2017-10-30 12:44:00 -07:00
plugins
scripts Add Backport to toolchain (#14525) (#14548) 2017-10-24 16:56:16 -04:00
src [6.x] Upgrade to webpack 3 (#14315) (#14824) 2017-11-07 15:54:48 -07:00
style_guides Update accessibility guide with note that it's valid to use aria-label directly on form elements. (#14361) 2017-10-11 09:51:10 -07:00
tasks [6.x] Upgrade to webpack 3 (#14315) (#14824) 2017-11-07 15:54:48 -07:00
test Add dashboard tests (#14775) (#14826) 2017-11-07 16:25:32 -05:00
ui_framework [6.x] Upgrade to webpack 3 (#14315) (#14824) 2017-11-07 15:54:48 -07:00
utilities
webpackShims [6.x] Upgrade to webpack 3 (#14315) (#14824) 2017-11-07 15:54:48 -07:00
.editorconfig
.eslintignore [flot-charts] move into ui/public (#14669) 2017-10-30 12:44:00 -07:00
.eslintrc [6.x] Use version 0.9.0 of eslint-config-kibana (#13183) 2017-08-01 12:00:44 +02:00
.gitignore gitignore npm-debug.log (#14797) 2017-11-06 14:45:38 -06:00
.node-version Bump node to 6.11.5 (#14568) 2017-10-25 09:26:59 -05:00
.npmrc
CONTRIBUTING.md Update CONTRIBUTING.md with information on how to focus the browser tests on a particular suite when running test:dev. (#14317) 2017-10-05 18:18:03 -07:00
FAQ.md
Gruntfile.js create babel-preset and babel-register modules (#13973) 2017-09-19 17:45:25 -07:00
LICENSE.md
package.json [6.x] Upgrade to webpack 3 (#14315) (#14824) 2017-11-07 15:54:48 -07:00
README.md Branching for 6.0: Bump version to 6.1.0 2017-07-24 15:31:28 -04:00
STYLEGUIDE.md Fix typo in accessibility styleguide link (#14718) (#14719) 2017-11-02 12:35:28 +01:00

Kibana 6.1.0

Kibana is your window into the Elastic Stack. Specifically, it's an open source (Apache Licensed), browser-based analytics and search dashboard for Elasticsearch.

Getting Started

If you just want to try Kibana out, check out the Elastic Stack Getting Started Page to give it a whirl.

If you're interested in diving a bit deeper and getting a taste of Kibana's capabilities, head over to the Kibana Getting Started Page.

Using a Kibana Release

If you want to use a Kibana release in production, give it a test run, or just play around:

Building and Running Kibana, and/or Contributing Code

You may want to build Kibana locally to contribute some code, test out the latest features, or try out an open PR:

Snapshot Builds

For the daring, snapshot builds are available. These builds are created nightly and have undergone no formal QA, so they should never be run in production. All builds are 64 bit.

platform
OSX tar
Linux tar deb rpm
Windows zip

Documentation

Visit Elastic.co for the full Kibana documentation.

Version Compatibility with Elasticsearch

Ideally, you should be running Elasticsearch and Kibana with matching version numbers. If your Elasticsearch has an older version number or a newer major number than Kibana, then Kibana will fail to run. If Elasticsearch has a newer minor or patch number than Kibana, then the Kibana Server will log a warning.

Note: The version numbers below are only examples, meant to illustrate the relationships between different types of version numbers.

Situation Example Kibana version Example ES version Outcome
Versions are the same. 5.1.2 5.1.2 💚 OK
ES patch number is newer. 5.1.2 5.1.5 ⚠️ Logged warning
ES minor number is newer. 5.1.2 5.5.0 ⚠️ Logged warning
ES major number is newer. 5.1.2 6.0.0 🚫 Fatal error
ES patch number is older. 5.1.2 5.1.0 ⚠️ Logged warning
ES minor number is older. 5.1.2 5.0.0 🚫 Fatal error
ES major number is older. 5.1.2 4.0.0 🚫 Fatal error

Questions? Problems? Suggestions?

  • If you've found a bug or want to request a feature, please create a GitHub Issue. Please check to make sure someone else hasn't already created an issue for the same topic.
  • Need help using Kibana? Ask away on our Kibana Discuss Forum and a fellow community member or Elastic engineer will be glad to help you out.