* Modify the relationships API and UI * Remove type validation on export * Update relationship test snapshots * Change relationships table titles * Change relationships UI to share one table * Add server side logic to inject meta data into saved objects from plugins * Manually enable each type of saved object to support * Use injected vars to determine what types are import / exportable * Fix some broken tests * Remove unused translations * Fix relationships mocha tests * Remove tests that ensured types are restricted, functionality removed * Move kfetch logic into separate file * Add inAppUrl to missing types * Add tooltip to management table titles that aren't links * Make relationships screen support filtering by type * Fix failing tests * Add refresh support for inAppUrls * Add error notifications when export API call fails * Add relationship direction * Fix broken tests * Remove graph workspace from import / export * Use parent / child terminology for relationships * Use direct relationship terminology * Flip view / edit logic in saved object management app * Make config saved object redirect to advanced settings * Fix broken tests * Remove unused translations * Code cleanup * Add tests * Add fallback overwrite confirmation object title * Enforce supported types on import, export and resolve import errors * Fix broken tests * Fix broken tests pt2 * Fix broken tests pt3 * Test cleanup * Use server.decorate to access savedobjectschemas * Fix some broken tests * Fix broken tests, add new title to relationships screen * Fix some broken tests * Handle dynamic versions * Fix inAppUrl structure in tests * Re-use generic canGoInApp * Fix broken tests * Apply maps PR feedback * Apply PR feedback pt1 * Apply PR feedback pt2 * Add savedObjectsManagement to uiExports * Fix broken tests * Fix encodeURIComponent implementation * Merge 403 and unsupported type errors into single error * Apply suggestion * Remove import / exportable by default, opt-in instead * Fix type config to show up properly in the table * Change config type title and fix tests * Remove isImportableAndExportable where set to false (new default) * Remove comments referencing to authorization * Add unit tests for spaces * Add unit tests for security plugin * Change can* signature to be the same as their equivalent function, apply PR feedback * Cleanup git diff * Revert "Change can* signature to be the same as their equivalent function, apply PR feedback" This reverts commit |
||
---|---|---|
.ci | ||
.github | ||
bin | ||
common/graphql | ||
config | ||
data | ||
docs | ||
licenses | ||
packages | ||
plugins | ||
rfcs | ||
scripts | ||
src | ||
style_guides | ||
tasks | ||
test | ||
typings | ||
utilities | ||
webpackShims | ||
x-pack | ||
.backportrc.json | ||
.browserslistrc | ||
.editorconfig | ||
.eslintignore | ||
.eslintrc.js | ||
.gitattributes | ||
.gitignore | ||
.i18nrc.json | ||
.node-version | ||
.nvmrc | ||
.prettierrc | ||
.sass-lint.yml | ||
.yarnrc | ||
CONTRIBUTING.md | ||
FAQ.md | ||
github_checks_reporter.json | ||
Gruntfile.js | ||
kibana.d.ts | ||
LICENSE.txt | ||
NOTICE.txt | ||
package.json | ||
preinstall_check.js | ||
README.md | ||
STYLEGUIDE.md | ||
tsconfig.browser.json | ||
tsconfig.json | ||
tsconfig.types.json | ||
TYPESCRIPT.md | ||
yarn.lock |
Kibana
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.
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.