Go to file
Shaunak Kashyap 32eff371f2 Getting Started page (#11805)
* Getting Started page (#11673)

* Initial code

* Renaming files/folders

* Notes and changes from HTML/CSS review

* CSS changes

* Fixing transform units

* Fleshing out logo circle

* Adding logos

* Un-nesting styles

* Adding kuiText class on <p> elements

* Making shield icon 404 go away

* Using trustAsHtml filter; using registry

* Adding code for registry

* Adding images

* Hooking up the opt-out link

* Fixing linter issues

* Fix issue with refresh bringing back nav

* Removing load_default module

* Use GETTING_STARTED_ROUTE constant

* Allow topMessage to be a directive

* Adding kuiLink CSS class to anchor elements

* Adding alt text to images

* Replace getters with regular methods

* Remove leftover comment

* Removing unnecessary comment

* Fixing typo in comment

* Adding comments for message properties

* Fixing typo in method name

* Defining custom CSS class

* Fixing method call

* Creating custom CSS classes

* Adding documentation links

* Use a instead of button for demo link

* Allow directives in manage and monitor messages

* Refactoring shared code into single ui/public/getting_started folder

* Adding README

* Fixing whitespace in/around links

* Trim messages before setting them

* Decorate in-app links with opt-out attribute

* Opt out of the Getting Started page if the user already has index patterns

* Adding more commentary around expectations of setTopMessage use

* Using ng-src and ng-href attributes where attr values are angular expressions

* Importing the directive before using it

* Using ui/registry for message registries

* Renaming service => helpers to clarify intent

* Adding explanatory comment

* Adding "or"

* Fixing div id

* Breaks out the inject logic into another directive

* Adding Getting Started page object for functional tests

* Consolidate into one registry

* Fixes incorrect classes

* Changes how styles are applied to injected-items items

* Modifying class name per CSS style guide

* Adding getting started doc link

* Removing unused import

* Attempting to fix breaking build

Apparently the Getting Started page is preventing access to Console (Dev Tools, really) so the functional tests for Console are failing. This commit opts the user out of the Getting Started page before attempting to navigate to Console.

* Cleanup on aisle testbed! (#11765)

* Navigate to getting started page so we can opt out of it
2017-05-15 14:04:16 -07:00
.github Add elasticsearch version to issue template 2016-07-25 11:00:27 -05:00
bin [plugin cli] Wrap arguments in quotes to preserve whitespace (#8945) 2016-11-17 10:10:24 -06:00
config Modifying SSL settings to be consistent with the stack (#9823) 2017-01-25 10:58:56 -05:00
data [folder structure] plugins/.data -> data 2016-07-05 14:06:16 -05:00
docs Update tutorial-load-dataset.asciidoc (#11703) 2017-05-12 08:44:46 -04: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
packages Kibana-related packages (#11308) 2017-04-19 04:31:00 -07:00
plugins [folder structure] plugins/.data -> data 2016-07-05 14:06:16 -05:00
scripts Convert makelogs and mocha npm scripts (#11665) 2017-05-09 10:53:10 -07:00
src Getting Started page (#11805) 2017-05-15 14:04:16 -07:00
style_guides Adds subdirectories section to architecture style guide (#11187) 2017-04-12 13:53:08 -05:00
tasks Remove legacy npm script that is no longer used or supported (#11796) 2017-05-15 14:56:23 -04:00
test Getting Started page (#11805) 2017-05-15 14:04:16 -07:00
ui_framework Update CardGroup component example to exhibit stacking on smaller screens. (#11751) 2017-05-11 15:10:15 -07:00
utilities Update visualRegression task to use Handlebars instead of DoT templates. 2016-06-21 10:42:49 -07:00
webpackShims Removing the destructuring and const from webpackShims (#11370) 2017-04-21 15:48:10 -04:00
.editorconfig Apply the same editorconfig rules to both markdown and asciidoc files 2016-09-07 11:41:41 -04:00
.eslintignore [webpack] fix loader query string usage (#9497) 2016-12-15 16:11:42 -07:00
.eslintrc [eslint] enable no undef (#10825) 2017-03-22 07:08:23 -07:00
.gitignore Tweaks needed for integrating with the functional test runner (#11469) 2017-04-27 09:01:54 -07:00
.node-version Bump node to 6.10.2 (#11039) 2017-04-10 15:26:16 -05:00
.npmrc Removes "global-style" setting for npm (#9256) 2016-11-29 15:43:57 -05:00
CONTRIBUTING.md Update contributing guidelines due to recent npm script changes (#11794) 2017-05-15 14:06:23 -04:00
FAQ.md propose language changes (#10709) 2017-03-05 12:10:32 -05:00
Gruntfile.js [functionalTestRunner] replace intern (#10910) 2017-04-11 17:01:06 -05:00
LICENSE.md [build] Add notice file (#10344) 2017-02-16 11:41:09 -05:00
package.json Remove legacy npm script that is no longer used or supported (#11796) 2017-05-15 14:56:23 -04:00
README.md bump version to 6.0.0-alpha2 2017-05-09 08:24:49 -04:00
STYLEGUIDE.md Fix architecture style guide link 2017-04-19 08:19:26 -05:00

Kibana 6.0.0-alpha2

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.

platform
OSX tar
Linux x64 tar deb rpm
Linux x86 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.