No description
Find a file
Court Ewing 59726c0b75
[optimizer] allow http caching for bundles (#15880) (#15933)
By setting cache-control to must-revalidate, we indicate to the browser
that it should send the if-none-match header with the last known etag
value. If the etags match, the server responds with a 304 and no body,
and if they don't the server responds with a 200 and a body along with a
new etag.

This ensures a cache is always invalidated when a bundle changes, like
when Kibana is upgraded or a plugin is installed.

We no longer send the last-modified header because we don't want the
browser caching based on time. Doing so can be unpredictable since the
browser may not agree with the server's definitions of DST, and the
server time itself can be changed.
2018-01-09 13:33:45 -05:00
.github github: PR template checklist in a comment 2017-08-12 10:31:33 -04:00
bin Adds keystore for securely storing settings (#14714) 2017-11-13 10:25:33 -08:00
config Kibana Home page - phase one (#14673) (#14733) 2017-11-02 14:11:24 -06:00
data
docs add time to visualization status (#15856) (#15894) 2018-01-08 10:55:00 -07:00
maps
packages [6.x] Upgrade to eslint 4 (#14862) (#14951) 2017-11-14 20:20:37 -07:00
plugins
scripts [6.x] [CI] Produce junit test reports (#15281) (#15437) 2017-12-05 18:21:38 -07:00
src [optimizer] allow http caching for bundles (#15880) (#15933) 2018-01-09 13:33:45 -05:00
style_guides Remove testing style guide. (#15699) (#15701) 2017-12-19 12:55:29 -08:00
tasks [6.x] [optimizer] run webpack compilation ASAP (no more laziness) (#15795) (#15917) 2018-01-09 10:09:44 -07:00
test [6.x] [functional/management/import] disable flaky test (#15914) (#15915) 2018-01-08 21:39:19 -07:00
ui_framework [KUI] Add defaultValue to KuiToolBarSearchBox (#15797) (#15825) 2018-01-03 14:32:51 +01:00
utilities [6.x] Upgrade to eslint 4 (#14862) (#14951) 2017-11-14 20:20:37 -07:00
webpackShims [6.x] Upgrade to eslint 4 (#14862) (#14951) 2017-11-14 20:20:37 -07:00
.backportrc.json Bump backport dependency and add .backportrc.json (#15417) (#15488) 2017-12-08 11:16:29 +01: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 Bumps node to 6.12.2 (#15612) 2017-12-15 10:16:10 -08: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 upgrade to eui 0.0.11 (#15870) (#15872) 2018-01-05 19:19:05 -07:00
README.md bump version to 6.2.0 2017-11-22 14:46:02 -05:00
STYLEGUIDE.md Fix typo in accessibility styleguide link (#14718) (#14719) 2017-11-02 12:35:28 +01:00

Kibana 6.2.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.