c639deba73
* Move all reporting tests into their own folder to allow for multiple kibana.yml configuration tests, including chromium * Add debugging and try to skip other tests an jenkins to speed things up * More debug output * more logging (remove other line which failed on jenkins) * Remove no sandbox flag, it doesn't help * Add fix for socket hangup and clean up tests * fix path to logstash_functional * Extend timeout for chromium, add verbose logging, add better comment, conditionally output curl command * fix path... again * Ah, other functional tests still need access to reporting page object, put it back * fix sp err * Add debug logs for screenshot stitching for png.bitblt error * Fix tests that don't pass logger to screenshotStitcher * Fix logger being undefined * Add more debug output * png has data, too much info to spit out * Add comment with link to issue for extra debug messages so they can be left in since so many passes * Dont use spawnSync with curl, use http.request instead, more support for it * Comment out chromium tests for now to avoid flakiness * Wait... lets at least make sure the other fix worked (the http.request instead of spawnsync and curl) * New http.request code doesn't seem to work on jenkins, timing out after 10 secs maybe * go back to spawnsync to see if it's an issue with the rxjs code or the http.request code * I think I figured it out... * Comment out tests to avoid flaky png error in the screenshot stitcher * Use a const for OSS archive path * use path.resolve correctly. |
||
|---|---|---|
| .github | ||
| bin | ||
| config | ||
| data | ||
| docs | ||
| licenses | ||
| packages | ||
| plugins | ||
| scripts | ||
| src | ||
| style_guides | ||
| tasks | ||
| test | ||
| utilities | ||
| webpackShims | ||
| x-pack | ||
| .backportrc.json | ||
| .editorconfig | ||
| .eslintignore | ||
| .eslintrc.js | ||
| .gitignore | ||
| .node-version | ||
| .nvmrc | ||
| .prettierrc | ||
| CONTRIBUTING.md | ||
| FAQ.md | ||
| Gruntfile.js | ||
| LICENSE.txt | ||
| NOTICE.txt | ||
| package.json | ||
| preinstall_check.js | ||
| README.md | ||
| STYLEGUIDE.md | ||
| tsconfig.json | ||
| tslint.yaml | ||
| yarn.lock | ||
Kibana 7.0.0-alpha1
Kibana is your window into the Elastic Stack. Specifically, it's a browser-based analytics and search dashboard for Elasticsearch.
- Getting Started
- Documentation
- Version Compatibility with Elasticsearch
- Questions? Problems? Suggestions?
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:
- Download the latest version on the Kibana Download Page.
- Learn more about Kibana's features and capabilities on the Kibana Product Page.
- We also offer a hosted version of Kibana on our Cloud Service.
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:
- CONTRIBUTING.md will help you get Kibana up and running.
- If you would like to contribute code, please follow our STYLEGUIDE.md.
- Learn more about our UI code with UI_SYSTEMS.md.
- For all other questions, check out the FAQ.md and wiki.
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 | default | OSS |
|---|---|---|
| OSX | tar | tar |
| Linux | tar deb rpm | tar deb rpm |
| Windows | zip | zip |
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.