No description
Find a file
Kibana Machine 4445dd7c90
[Security Solution] - Updating UI to work with new kibana privileges abstraction on alerts (#108961) (#109156)
## Summary

Holy moly. 

What is happening in this PR? 🤷🏽‍♀️ Let's break it down:
- Added a package `@kbn/alerts` - another one?! ...yes
  - This is meant to add shared hooks and components around alerts as data
  - `useGetUserAlertsPermissions` - accepts the Kibana capabilities object and returns whether the user has `read` and `crud` alerts privileges
  - `AlertsFeatureNoPermissions` - component displayed when user does not have alerts privileges
- UI changes for user with NO alerts privileges
  - `Alerts` tab hidden in security solution side navigation
  - `Alerts` tab hidden in rule details page  
- UI changes for user with alerts READ ONLY privileges
  - alerts checkboxes hidden in alerts table
  - alerts bulk actions hidden in alerts table

Co-authored-by: Yara Tercero <yctercero@users.noreply.github.com>
2021-08-18 17:19:37 -04:00
.buildkite
.ci
api_docs
config
dev_docs [NoDataPage] Updating the default messages (#108799) (#109006) 2021-08-17 20:27:39 -04:00
docs [Elasticsearch] remove legacy es client (#107619) (#109144) 2021-08-18 15:41:25 -04:00
examples Adding owners to kibana plugins (#108407) (#108919) 2021-08-17 12:49:33 -04:00
licenses
packages [Security Solution] - Updating UI to work with new kibana privileges abstraction on alerts (#108961) (#109156) 2021-08-18 17:19:37 -04:00
plugins
rfcs
scripts
src text improvement (#109111) (#109145) 2021-08-18 15:48:32 -04:00
tasks/config
test [Elasticsearch] remove legacy es client (#107619) (#109144) 2021-08-18 15:41:25 -04:00
typings
utilities
vars
x-pack [Security Solution] - Updating UI to work with new kibana privileges abstraction on alerts (#108961) (#109156) 2021-08-18 17:19:37 -04:00
.backportrc.json chore(NA): adds 7.16 into backportrc (#109128) (#109136) 2021-08-18 12:57:02 -04:00
.bazelignore
.bazeliskversion
.bazelrc
.bazelrc.common
.bazelversion
.browserslistrc
.editorconfig
.eslintignore
.eslintrc.js
.fossa.yml
.gitattributes
.gitignore
.i18nrc.json [Security Solution] - Updating UI to work with new kibana privileges abstraction on alerts (#108961) (#109156) 2021-08-18 17:19:37 -04:00
.node-version
.npmrc
.nvmrc
.prettierignore
.prettierrc
.stylelintignore
.stylelintrc
.telemetryrc.json
.yarnrc
api-documenter.json
BUILD.bazel
CONTRIBUTING.md Point to new developer guide in CONTRIBUTING.md (#108953) (#108970) 2021-08-17 14:42:05 -04:00
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 [Security Solution] - Updating UI to work with new kibana privileges abstraction on alerts (#108961) (#109156) 2021-08-18 17:19:37 -04:00
preinstall_check.js
README.md
renovate.json5
STYLEGUIDE.mdx
tsconfig.base.json
tsconfig.bazel.json
tsconfig.browser.json
tsconfig.browser_bazel.json
tsconfig.json
tsconfig.types.json
TYPESCRIPT.md
WORKSPACE.bazel
yarn.lock [Security Solution] - Updating UI to work with new kibana privileges abstraction on alerts (#108961) (#109156) 2021-08-18 17:19:37 -04: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.