e38501500e
* Added the following components: - highlight details (with render test) - searchprofiler tabs - (wip) profile tree - (wip) shard details * First iteration of ProfileTree component (needs render test) * Remove space * ProfileTree render test * Add profile tree test to git index * First iteration of editor component with render test * First iteration of nearly functional public * Fix highlight_details_flyout render test * Move NP directory to public and fix import issue created by directly importing FormattedMessage * Rendering and looking more normal * Fix type issues and fix a11y for ace editor * Added ability to do profile requests again and render into UI (styling WiP) * Fix props in editor test * Added empty tree placeholder component (with test), moved styling around into individual files (wip) * Fix path * Lots of style updates and added util for determining visible children (+test) * Re-add missing badge and make it slightly wider (otherwise 100.00% cuts off to 100.0...) * Delete legacy public! * SCSS refactor + fix for re-rendering editor * UI and server updates after license checks * [skip ci] Add server np_ready code * fix i18n * Re-enable error annotations * Minor UX improvements (focus editor after failed request and no tabindex for textarea without active license) Added some spaces to make code more readable * Removed xpackMain from ServerShim Updated use of notifications -> notifications.toasts from np core setup Removed TODO for using core.application.register (not available for legacy apps) * Added placeholder component for loading state and implemented useReducer * Refactor actions * Changes after PR feedback: - TS for unsafe utils test fixtures - Safer use of .selfTime (no more NaN) - Sentence case where applicable - Cleaned up TODOs - Fix styling issue with percentage on badges of profile tree - Refactor name of profile hook (now useRequestProfile) - Fixed copy paste issue in highlight flyout `Total time` -> `Self time` - Restyled the profile button to be fill and not take up the full horizontal space - Removed the `Type` input from the profiler query section * Removed .type from backend and cleanup translations * Disable responsive UI layout for now * Remove buggy error annotation code * - Refactored percentage badge to own component - Updated styles after testing on IE11 - Updated styles after testing on Safari - Chrome and FF worked on this commit * Update missing i18n and fix use ace ui keyboard hook * Update useEffect dependencies array for editor component * Use absolute path to dev tools app (to fix CI) * Remove file extensions * Re-add missing data-test-subj |
||
|---|---|---|
| .ci | ||
| .github | ||
| bin | ||
| common/graphql | ||
| config | ||
| data | ||
| docs | ||
| licenses | ||
| packages | ||
| rfcs | ||
| scripts | ||
| src | ||
| style_guides | ||
| tasks | ||
| test | ||
| typings | ||
| utilities | ||
| vars | ||
| 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 | ||
| Jenkinsfile | ||
| kibana.d.ts | ||
| LICENSE.txt | ||
| NOTICE.txt | ||
| package.json | ||
| preinstall_check.js | ||
| README.md | ||
| renovate.json5 | ||
| 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.