Go to file
Spencer f71ec29bd6
[CI] Produce junit test reports (#15281)
* [mocha] use custom reporter for legible results in jenkins

* [jest] use custom result processor for legible results in jenkins

* [karma] enable junit output on CI

* [mocha/junitReporter] accept rootDirectory as configuration

* [jest/reporter] use reporters option added in jest 20

* [toolingLog] remove black/white specific colors

* [dev/mocha/junit] no reason for junit to be a "reporter"

* typos

* [dev/mocha/junit] use else if

* [karma/junit] use string#replace for explicitness

* [junit] use test file path as "classname"

* [ftr/mocha] no longer a "console" specific reporter
2017-12-05 17:29:48 -07:00
.github github: PR template checklist in a comment 2017-08-12 10:28:21 -04:00
bin Remove node fallback from kibana-keystore (#15066) 2017-11-27 10:11:38 -06:00
config Kibana Home page - phase one (#14673) 2017-11-02 12:58:46 -06:00
data [folder structure] plugins/.data -> data 2016-07-05 14:06:16 -05:00
docs Region map settings clarifications (#14893) (#15421) 2017-12-05 15:01:48 -05:00
packages Upgrade to eslint 4 (#14862) 2017-11-14 18:16:59 -07:00
plugins [folder structure] plugins/.data -> data 2016-07-05 14:06:16 -05:00
scripts [CI] Produce junit test reports (#15281) 2017-12-05 17:29:48 -07:00
src [CI] Produce junit test reports (#15281) 2017-12-05 17:29: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:50:32 -07:00
tasks [CI] Produce junit test reports (#15281) 2017-12-05 17:29:48 -07:00
test [CI] Produce junit test reports (#15281) 2017-12-05 17:29:48 -07:00
ui_framework Add disabled option for kuiContextMenuItems (#15119) 2017-11-29 16:51:10 -05:00
utilities Upgrade to eslint 4 (#14862) 2017-11-14 18:16:59 -07:00
webpackShims Upgrade to eslint 4 (#14862) 2017-11-14 18:16:59 -07:00
.editorconfig Apply the same editorconfig rules to both markdown and asciidoc files 2016-09-07 11:41:41 -04:00
.eslintignore [flot-charts] move into ui/public (#14669) 2017-10-30 12:43:12 -07:00
.eslintrc Use version 0.9.0 of eslint-config-kibana (#13177) 2017-07-28 18:03:34 +02:00
.gitignore gitignore npm-debug.log (#14797) 2017-11-06 14:36:28 -06:00
.node-version Bump node to 6.11.5 (#14568) 2017-10-25 09:26:00 -05:00
.npmrc Removes "global-style" setting for npm (#9256) 2016-11-29 15:43:57 -05:00
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:17:05 -07:00
FAQ.md propose language changes (#10709) 2017-03-05 12:10:32 -05:00
Gruntfile.js create babel-preset and babel-register modules (#13973) 2017-09-19 17:44:47 -07:00
LICENSE.md [build] Add notice file (#10344) 2017-02-16 11:41:09 -05:00
package.json [CI] Produce junit test reports (#15281) 2017-12-05 17:29:48 -07:00
README.md Change may to might in Readme (#15099) 2017-11-21 14:18:42 -08:00
STYLEGUIDE.md Fix typo in accessibility styleguide link (#14718) 2017-11-02 12:28:22 +01:00

Kibana 7.0.0-alpha1

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 might 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.