No description
Find a file
Nathan Reese 30cc42f4ba Input Control visualization (#13314)
* react editor example

* ensure props are not updated

* use new stageEditorParams method to stage parameter changes

* make component stateless

* use terms_vis_editor component

* get add button to work

* update vis controller to display terms input controls

* update componenent when query bar updates

* add functional test

* lay ground work for different control types in single visulization

* make editors for range and text controls

* text control

* implement type ahead suggestor for text control

* add range slider

* some CSS work

* add submit button, move control init functionallity under control_factory

* add custom options for control types

* provide buttons to move controls up and down

* Make ControlEditor component and clean up styling of editor

* styling work

* multi select for terms dropdown control

* add option to disable filter staging, only enable submit button when filters are staged

* clean up range styling

* rename top level vis folder

* cleanup

* move control type select out of each control editor

* dark theme styling

* use ui/public/filter_manager/lib/phrases.js to build phrases filter, add tests to range filter manager

* use savedObjectsClient to get index patterns

* remove text control and add id to controls for react tracking

* ensure fields get updated when index pattern changes

* update PropTypes for react 15.6.1

* update to latest react-select to avoid isMounted deprecation warnings

* fix input controls functional test

* rename termsControl to listControl to be more generic

* add function test for clear button, refactor directory structure

* functional tests for updateFiltersOnChange is true

* fix react-select clipping problem in dashboard

* try clicking option instead of pressing enter to set react-select value in functional tests

* react-select css

* clean up control_editor component, make ListControlEditor component be function

* add jest test for vis_editor component and accessibility

* add decimal places option to range slider

* add jest test for InputControlVis component

* add default to switch blocks, split editor into seperate tabs, use shallow in snapshot tests

* fix race condition in field_select, update index_pattern_select to fetch indexPatterns on each filter

* clean up control initialization

* use htmlIdGenerator to avoid html element id conflicts

* update functional test to support new editor tabs

* finish jest tests for sub componenets

* mark vis as experimental, refactor buttons for better usability

* fix bug in list control where unable to select options containing numbers and options containing commas. Truncate display of long list options

* fix chart types functional test

* fix jest tests, add margin to action buttons

* remove binds from render functions

* experement with native input range sliders

* Revert "experement with native input range sliders"

This reverts commit aed599e88a.

* Use Promise.resolve in tests and replace _createRequest with searchSource.fetch

* add inputs to range control
2017-09-20 06:22:55 -06:00
.github github: PR template checklist in a comment 2017-08-12 10:28:21 -04:00
bin Always set NODE_ENV to production (#12010) 2017-05-26 11:27:16 -04:00
config
data
docs [DOCS] Added index-shared6 Remove index-shared11 2017-09-19 10:38:49 -07:00
packages Upgrade to Jest 21 (#13863) 2017-09-07 12:06:55 +02:00
plugins
scripts create babel-preset and babel-register modules (#13973) 2017-09-19 17:44:47 -07:00
src Input Control visualization (#13314) 2017-09-20 06:22:55 -06:00
style_guides Update react style guide (#13958) 2017-09-12 15:57:35 -04:00
tasks create babel-preset and babel-register modules (#13973) 2017-09-19 17:44:47 -07:00
test Input Control visualization (#13314) 2017-09-20 06:22:55 -06:00
ui_framework Move htmlIdGenerator to ui_framework (#13906) 2017-09-11 13:22:32 +02:00
utilities Use es6 exports, replace module.exports (#12084) 2017-06-06 10:11:59 -07:00
webpackShims Removes webpack-directory-name-as-main dependency (#13584) 2017-08-23 08:21:32 -07:00
.editorconfig
.eslintignore [eslint] Ignore ui_framework/doc_site/build (#12400) 2017-06-26 18:07:44 -05:00
.eslintrc Use version 0.9.0 of eslint-config-kibana (#13177) 2017-07-28 18:03:34 +02:00
.gitignore Ignore package-lock.json (#13731) 2017-08-28 11:10:59 -05:00
.node-version bump node.js to version 6.11.1 (#12776) 2017-07-11 17:57:01 -04:00
.npmrc
CONTRIBUTING.md Added a link to the Microsoft VSCode ESLint tool in the CONTRIBUTING.md (#13827) 2017-09-06 15:23:20 -04: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
package.json Input Control visualization (#13314) 2017-09-20 06:22:55 -06:00
README.md Branching for 6.0: bump version to 7.0.0-alpha1 2017-07-24 15:24:56 -04:00
STYLEGUIDE.md Initial version of accessibility guide (#13390) 2017-08-14 07:42:06 +02: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 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.