No description
Find a file
Vadim Yakhin a9a834a105
[Workplace Search] Add Account Settings page imported from Security plugin (#99791)
* Copy lazy_wrapper and suspense_error_boundary from Spaces plugin

These components are needed to enable async loading of Security components into Enterprise Search.

The components are copied without any changes except for i18n ids, so it's easier to DRY out in the future if needed.

* Create async versions of personal_info and change_password components

* Create ui_api that allows to load Security components asuncronously

The patterns were mostly copied from Spaces plugin

* Make ui_api available through Security components's lifecycle methods

* Import Security plugin into Enterprise Search

* Add Security plugin and Notifications service to Kibana Logic file

* Export the required components from the Security plugin and
use them in the new AccountSettings component

* Update link to the Account Settings page

* Move getUiApi call to security start and pass core instead of getStartServices

* Simplify import of change_password_async component by providing...
... `notifications` and `userAPIClient` props in the security plugin

* Remove UserAPIClient from ui_api

It's not needed anymore since the components are initiated with this prop already passed

* Export ChangePasswordProps and PersonalInfoProps from account_management/index.ts

This makes it easier to import these props from outside the account_management folder

* Remove notifications service from kibana_logic

It is not needed anymore since we're initializing security components with notifications already provided

* Add UiApi to SecurityPluginStart interface

* Utilize index files for exporting Props types

* Replace Pick<...> with two separate interfaces as it doesn't work well with our docs

* Add a comment explaining why we're not loading async components through index file
2021-06-10 14:20:30 -03:00
.buildkite
.ci
.github [ML] Move Index Data Visualizer into separate plugin (Part 1) (#100922) 2021-06-08 14:50:14 -05:00
api_docs Small clean up with Cases plugin API (#101668) 2021-06-10 08:43:07 -04:00
config
dev_docs
docs [Expressions] Create expressions function to get UI settings (#101317) 2021-06-10 15:17:52 +02:00
examples [Index patterns] Field editor example app (#100524) 2021-06-09 14:44:27 -05:00
licenses
packages [Lens] Formula editor (#99297) 2021-06-10 10:09:16 -04:00
plugins
rfcs
scripts
src [plugin cli] Remove settings argument from warnings log (#101824) 2021-06-10 12:03:37 -05:00
tasks/config
test skip flaky runtime fields test. #100966 2021-06-10 12:00:38 -05:00
typings Update @elastic/elasticsearch to 8.0.0-canary13 (#98266) 2021-06-08 15:06:06 +02:00
utilities
vars
x-pack [Workplace Search] Add Account Settings page imported from Security plugin (#99791) 2021-06-10 14:20:30 -03:00
.backportrc.json
.bazelignore
.bazeliskversion
.bazelrc
.bazelrc.common
.bazelversion
.browserslistrc
.editorconfig
.eslintignore
.eslintrc.js [Enterprise Search] Mocks/tests tech debt - avoid hungry mocking (#101107) 2021-06-08 21:36:06 -07:00
.fossa.yml
.gitattributes
.gitignore
.i18nrc.json
.node-version
.npmrc
.nvmrc
.prettierignore
.prettierrc
.stylelintignore
.stylelintrc
.telemetryrc.json
.yarnrc
api-documenter.json
BUILD.bazel
CODE_OF_CONDUCT.md
CONTRIBUTING.md
FAQ.md
github_checks_reporter.json
Gruntfile.js
Jenkinsfile
jest.config.integration.js
jest.config.js
kibana.d.ts
LICENSE.txt
NOTICE.txt
package.json chore(NA): moving @kbn/server-route-repository into bazel (#101484) 2021-06-09 21:39:31 +01:00
preinstall_check.js
README.md
renovate.json5
RISK_MATRIX.mdx
SECURITY.md
STYLEGUIDE.mdx
tsconfig.base.json
tsconfig.browser.json
tsconfig.json
tsconfig.refs.json [ts] migrate x-pack/test to composite ts project (#101441) 2021-06-08 12:54:05 -04:00
tsconfig.types.json
TYPESCRIPT.md
WORKSPACE.bazel
yarn.lock chore(NA): moving @kbn/server-route-repository into bazel (#101484) 2021-06-09 21:39:31 +01:00

Kibana

Kibana is your window into the Elastic Stack. Specifically, it's a 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 might want to build Kibana locally to contribute some code, test out the latest features, or try out an open PR:

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.