Go to file
Spencer 4b0893ac6e
[babel-register] ignore packages directory when running from source (#26098)
When running the Kibana distributable packages are excluded from `babel-register` because they are installed in the node_modules directory. When running from source they are not ignored, which means that babel-register is doing more work than necessary because these files need to already be built. To fix this I've added an ignore rule that excludes all packages when we are running from source.
2018-11-22 18:14:14 -08:00
.ci [ci] load the boostrap_cache baked into CI images (#25841) 2018-11-20 14:22:44 -08:00
.github Add APM UI to codeowners (#25218) 2018-11-07 10:27:29 +01:00
bin [bin/windows] Remove title (#21567) 2018-08-03 06:53:54 -05:00
config Set kibana locale in kibana.yml config (#21201) 2018-08-02 14:43:22 +03:00
data [folder structure] plugins/.data -> data 2016-07-05 14:06:16 -05:00
docs New visualization type selection (#23833) 2018-11-22 12:52:05 +01:00
licenses Migrate x-pack-kibana source to kibana 2018-04-24 13:48:10 -07:00
packages Move buildEsQuery to a package (#23345) 2018-11-22 15:24:19 +01:00
plugins [folder structure] plugins/.data -> data 2016-07-05 14:06:16 -05:00
scripts Remove husky (#24887) 2018-11-15 01:34:45 +00:00
src [babel-register] ignore packages directory when running from source (#26098) 2018-11-22 18:14:14 -08:00
style_guides Update js_style_guide.md 2018-10-25 16:27:36 -05:00
tasks Move buildEsQuery to a package (#23345) 2018-11-22 15:24:19 +01:00
test New visualization type selection (#23833) 2018-11-22 12:52:05 +01:00
utilities Apache 2.0 license headers (#19383) 2018-05-28 20:06:30 -07:00
webpackShims add polyfill for ChildNode remove (#21797) 2018-08-10 15:21:11 -06:00
x-pack remove x-pack/yarn.lock, accidentally added back in #23345 2018-11-22 12:51:41 -08:00
.backportrc.json [backport] add back earlier 6.x minor versions 2018-10-26 11:05:30 -04:00
.browserslistrc Convert all Less files to Sass in Dashboard, using EUI variable scope (#21374) 2018-08-14 19:05:33 -04:00
.editorconfig Apply the same editorconfig rules to both markdown and asciidoc files 2016-09-07 11:41:41 -04:00
.eslintignore Move buildEsQuery to a package (#23345) 2018-11-22 15:24:19 +01:00
.eslintrc.js [canvas] move yarn scripts to node scripts (#25258) 2018-11-07 10:53:06 -08:00
.gitignore [kbn-interpreter] ignore plugin build directory 2018-11-20 08:05:20 -08:00
.i18nrc.json [I18n] Translate Graph (#23987) 2018-11-22 13:41:03 +03:00
.node-version Bump node to 8.11.4 (#22048) 2018-08-16 13:05:17 -05:00
.nvmrc Bump node to 8.11.4 (#22048) 2018-08-16 13:05:17 -05:00
.prettierrc Increase prettier line width to 100 (#20535) 2018-07-09 22:50:37 +02:00
.yarnrc [kbn-pm] Use yarn workspaces for dependencies (#24095) 2018-11-12 12:38:11 -06:00
CONTRIBUTING.md Update "Debugging server code" instructions in CONTRIBUTING.md (#25397) 2018-11-08 13:15:03 -07:00
FAQ.md propose language changes (#10709) 2017-03-05 12:10:32 -05:00
Gruntfile.js Apache 2.0 license headers (#19383) 2018-05-28 20:06:30 -07:00
LICENSE.txt Migrate x-pack-kibana source to kibana 2018-04-24 13:48:10 -07:00
NOTICE.txt Graph LESS to SASS (#23348) 2018-09-20 09:35:22 -04:00
package.json Move buildEsQuery to a package (#23345) 2018-11-22 15:24:19 +01:00
preinstall_check.js Apache 2.0 license headers (#19383) 2018-05-28 20:06:30 -07:00
README.md Remove version and snapshots from readme (#25747) 2018-11-15 17:49:36 -05:00
STYLEGUIDE.md Add a typescript readme (#23841) 2018-10-17 08:10:48 -04:00
tsconfig.browser.json [typescript] continue to use the default config in development (#21966) 2018-08-14 15:27:07 -07:00
tsconfig.json Feature/dashboard translations (#24328) 2018-11-20 10:19:20 +03:00
tsconfig.types.json Add Kibana bootstrap step to generate types exposed by the core and its plugins. (#23686) 2018-10-05 21:00:26 +02:00
tslint.yaml Upgrade to TypeScript 3 (#22792) 2018-09-11 08:38:41 +03:00
TYPESCRIPT.md Add a typescript readme (#23841) 2018-10-17 08:10:48 -04:00
yarn.lock [APM] Migrate to Typescript and refactor backend apis (#25848) 2018-11-22 10:30:25 +01:00

Kibana

Kibana is your window into the Elastic Stack. Specifically, it's a 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:

Documentation

Visit Elastic.co for the full Kibana documentation.

For information about building the documentation, see the README in elastic/docs.

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.