Your window into the Elastic Stack
Find a file
spalger 7460c0ac2d [agg_response/point_series] always assign series labels to points
Since forever, the vislib has been compensating for a behavior/bug in the agg_response module where "series" labels were not assigned to points if there wasn't a "series" aggregation or multiple y-axis. To compensate for this, the vislib was assigning the yAxisLabel to the series, which had the same effect, but now that the legend is rendered in it's own tick, followed by the visualization, and that behavior was being executed during the vislib render, the legend has been flashing an empty row for a while (this was worsened by the fact that vislib rendering did not trigger a digest cycle).

These changes remove the workaround code from the vislib, and update the agg_response to always send the y-axis label as the series label when there is no series aggregation. Behavior with multiple-y-axis and multiple series aggs should be preserved.
2016-10-13 13:32:57 -07:00
.github Add elasticsearch version to issue template 2016-07-25 11:00:27 -05:00
bin Revert "Limit memory overhead" 2016-04-28 15:13:41 -07:00
config remove leading spaces 2016-09-22 14:18:54 -04:00
data [folder structure] plugins/.data -> data 2016-07-05 14:06:16 -05:00
docs typo fix for advanced-settings.asciidoc 2016-10-13 10:08:25 +08:00
maps Point kibana map config at tiles.elastic.co AWS. 2016-07-25 16:20:54 -07:00
optimize [optimize] ensure the optimize directory exists with a .empty file 2015-11-02 10:36:20 -06:00
plugins [folder structure] plugins/.data -> data 2016-07-05 14:06:16 -05:00
src [agg_response/point_series] always assign series labels to points 2016-10-13 13:32:57 -07:00
style_guides Update CSS style guide with new state class format. Change examples to use component name instead of namespace. 2016-07-26 16:12:37 -07:00
tasks [tests/functional] auto-rebuild assets in test:ui:server task 2016-09-19 13:16:39 -07:00
test Merge pull request #8558 from thomasneirynck/chore/cleanup-test 2016-10-05 18:45:08 -04:00
utilities Update visualRegression task to use Handlebars instead of DoT templates. 2016-06-21 10:42:49 -07:00
webpackShims Replace compiled angular-bootstrap file with original HTML and JS source files. 2016-07-05 12:27:20 -07:00
.editorconfig Apply the same editorconfig rules to both markdown and asciidoc files 2016-09-07 11:41:41 -04:00
.eslintignore Fix redefined variables 2016-08-12 14:52:43 -07:00
.eslintrc Move conflicting dot files 2016-08-12 14:28:00 -07:00
.gitignore Merge pull request #8340 from spalger/dev/functional/auto-rebuild-devserver 2016-09-19 13:52:00 -07:00
.node-version Bump node version to 6.7.0 2016-10-10 05:57:25 -05:00
.npmrc Add .npmrc, save exact package versions 2015-11-11 11:46:52 -06:00
.travis.yml add travis config 2016-03-10 23:13:02 -07:00
CONTRIBUTING.md Update contributing guide to be explicit about creating a fork first 2016-09-15 16:14:18 -04:00
FAQ.md Fix broken links in FAQ.md 2016-02-11 22:42:53 +01:00
Gruntfile.js Fix redefined variables 2016-08-12 14:52:43 -07:00
LICENSE.md Make compatible with kibana core 2016-08-12 14:14:04 -07:00
package.json Bump node version to 6.7.0 2016-10-10 05:57:25 -05:00
README.md Update README to clarify that the version numbers in the compatibility chart are only examples. 2016-09-14 18:22:58 -07:00
STYLEGUIDE.md Make links in STYLEGUIDE relative. 2016-06-09 19:03:19 -07:00

Kibana 6.0.0-alpha1

Kibana is an open source (Apache Licensed), browser based analytics and search dashboard for Elasticsearch. Kibana is a snap to setup and start using. Kibana strives to be easy to get started with, while also being flexible and powerful, just like Elasticsearch.

Requirements

  • Elasticsearch master
  • Kibana binary package

Installation

Upgrade from previous version

  • Move any custom configurations in your old kibana.yml to your new one
  • Reinstall plugins
  • Start or restart Kibana

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 🚫 Fatal error
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

Quick Start

You're up and running! Fantastic! Kibana is now running on port 5601, so point your browser at http://YOURDOMAIN.com:5601.

The first screen you arrive at will ask you to configure an index pattern. An index pattern describes to Kibana how to access your data. We make the guess that you're working with log data, and we hope (because it's awesome) that you're working with Logstash. By default, we fill in logstash-* as your index pattern, thus the only thing you need to do is select which field contains the timestamp you'd like to use. Kibana reads your Elasticsearch mapping to find your time fields - select one from the list and hit Create.

Congratulations, you have an index pattern! You should now be looking at a paginated list of the fields in your index or indices, as well as some informative data about them. Kibana has automatically set this new index pattern as your default index pattern. If you'd like to know more about index patterns, pop into to the Settings section of the documentation.

Did you know: Both indices and indexes are acceptable plural forms of the word index. Knowledge is power.

Now that you've configured an index pattern, you're ready to hop over to the Discover screen and try out a few searches. Click on Discover in the navigation bar at the top of the screen.

Documentation

Visit Elastic.co for the full Kibana documentation.

Snapshot Builds

For the daring, snapshot builds are available. These builds are created after each commit to the master branch, and therefore are not something you should run in production.

platform
OSX tar
Linux x64 tar deb rpm
Linux x86 tar deb rpm
Windows zip