# Backport This will backport the following commits from `main` to `8.5`: - [[Security Solution][Bug fix] alerts table over 10k results (#145441)](https://github.com/elastic/kibana/pull/145441) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"christineweng","email":"18648970+christineweng@users.noreply.github.com"},"sourceCommit":{"committedDate":"2022-11-16T23:38:43Z","message":"[Security Solution][Bug fix] alerts table over 10k results (#145441)\n\nThis PR aims to address:\r\n- https://github.com/elastic/kibana/issues/142965\r\n\r\n### Background\r\nOn Alerts page -> Events table -> Event Rendered view, when there are\r\nover 10,000 alerts, upon clicking the last page, a warning message\r\nappears.\r\n\r\n<img width=\"800\" alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/18648970/202265598-5d9d657c-4918-408e-9f92-bcaafc904757.png\">\r\n\r\nThe pop up is expected behavior according to documentation from:\r\nhttps://www.elastic.co/guide/en/elasticsearch/reference/current/paginate-search-results.html\r\n.\r\n\r\n> By default, you cannot use from and size to page through more than\r\n10,000 hits. This limit is a safeguard set by the\r\n[index.max_result_window](https://www.elastic.co/guide/en/elasticsearch/reference/current/index-modules.html#index-max-result-window)\r\nindex setting.\r\n\r\n\r\n### After\r\nCurrently the Grid view has a safeguard in place, where if there are\r\nmore than 10k results, it will not show the last page, hence preventing\r\nuser from clicking it and seeing the error pop up.\r\n- This PR applies the same approach by wrapping the `EventRenderView`\r\ncomponent with the `EuiDataGridContainer`.\r\n- This PR also renamed `EuiDataGridContainer` to\r\n`EuiEventTableContainer` to indicate broader use.\r\n\r\nWhen there are over 10k records, last page is not available in\r\npagination, and it is the same in Event Rendered View as in Grid view:\r\n\r\n\r\n\r\n\r\nhttps://user-images.githubusercontent.com/18648970/202271379-309cbb3c-5da6-4c46-9814-beeca39d1f36.mov","sha":"3c77ec063387ee1c7545774d069f134d55eabe2b","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","v6.8.6","Team:Threat Hunting","Team: SecuritySolution","Team:Threat Hunting:Investigations","v8.7.0"],"number":145441,"url":"https://github.com/elastic/kibana/pull/145441","mergeCommit":{"message":"[Security Solution][Bug fix] alerts table over 10k results (#145441)\n\nThis PR aims to address:\r\n- https://github.com/elastic/kibana/issues/142965\r\n\r\n### Background\r\nOn Alerts page -> Events table -> Event Rendered view, when there are\r\nover 10,000 alerts, upon clicking the last page, a warning message\r\nappears.\r\n\r\n<img width=\"800\" alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/18648970/202265598-5d9d657c-4918-408e-9f92-bcaafc904757.png\">\r\n\r\nThe pop up is expected behavior according to documentation from:\r\nhttps://www.elastic.co/guide/en/elasticsearch/reference/current/paginate-search-results.html\r\n.\r\n\r\n> By default, you cannot use from and size to page through more than\r\n10,000 hits. This limit is a safeguard set by the\r\n[index.max_result_window](https://www.elastic.co/guide/en/elasticsearch/reference/current/index-modules.html#index-max-result-window)\r\nindex setting.\r\n\r\n\r\n### After\r\nCurrently the Grid view has a safeguard in place, where if there are\r\nmore than 10k results, it will not show the last page, hence preventing\r\nuser from clicking it and seeing the error pop up.\r\n- This PR applies the same approach by wrapping the `EventRenderView`\r\ncomponent with the `EuiDataGridContainer`.\r\n- This PR also renamed `EuiDataGridContainer` to\r\n`EuiEventTableContainer` to indicate broader use.\r\n\r\nWhen there are over 10k records, last page is not available in\r\npagination, and it is the same in Event Rendered View as in Grid view:\r\n\r\n\r\n\r\n\r\nhttps://user-images.githubusercontent.com/18648970/202271379-309cbb3c-5da6-4c46-9814-beeca39d1f36.mov","sha":"3c77ec063387ee1c7545774d069f134d55eabe2b"}},"sourceBranch":"main","suggestedTargetBranches":["6.8"],"targetPullRequestStates":[{"branch":"6.8","label":"v6.8.6","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/145441","number":145441,"mergeCommit":{"message":"[Security Solution][Bug fix] alerts table over 10k results (#145441)\n\nThis PR aims to address:\r\n- https://github.com/elastic/kibana/issues/142965\r\n\r\n### Background\r\nOn Alerts page -> Events table -> Event Rendered view, when there are\r\nover 10,000 alerts, upon clicking the last page, a warning message\r\nappears.\r\n\r\n<img width=\"800\" alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/18648970/202265598-5d9d657c-4918-408e-9f92-bcaafc904757.png\">\r\n\r\nThe pop up is expected behavior according to documentation from:\r\nhttps://www.elastic.co/guide/en/elasticsearch/reference/current/paginate-search-results.html\r\n.\r\n\r\n> By default, you cannot use from and size to page through more than\r\n10,000 hits. This limit is a safeguard set by the\r\n[index.max_result_window](https://www.elastic.co/guide/en/elasticsearch/reference/current/index-modules.html#index-max-result-window)\r\nindex setting.\r\n\r\n\r\n### After\r\nCurrently the Grid view has a safeguard in place, where if there are\r\nmore than 10k results, it will not show the last page, hence preventing\r\nuser from clicking it and seeing the error pop up.\r\n- This PR applies the same approach by wrapping the `EventRenderView`\r\ncomponent with the `EuiDataGridContainer`.\r\n- This PR also renamed `EuiDataGridContainer` to\r\n`EuiEventTableContainer` to indicate broader use.\r\n\r\nWhen there are over 10k records, last page is not available in\r\npagination, and it is the same in Event Rendered View as in Grid view:\r\n\r\n\r\n\r\n\r\nhttps://user-images.githubusercontent.com/18648970/202271379-309cbb3c-5da6-4c46-9814-beeca39d1f36.mov","sha":"3c77ec063387ee1c7545774d069f134d55eabe2b"}}]}] BACKPORT--> Co-authored-by: christineweng <18648970+christineweng@users.noreply.github.com> |
||
---|---|---|
.buildkite | ||
.ci | ||
.github | ||
api_docs | ||
config | ||
dev_docs | ||
docs | ||
examples | ||
kbn_pm | ||
legacy_rfcs | ||
licenses | ||
packages | ||
plugins | ||
scripts | ||
src | ||
test | ||
typings | ||
vars | ||
x-pack | ||
.backportrc.json | ||
.bazelignore | ||
.bazeliskversion | ||
.bazelrc | ||
.bazelrc.common | ||
.bazelversion | ||
.browserslistrc | ||
.editorconfig | ||
.eslintignore | ||
.eslintrc.js | ||
.gitattributes | ||
.gitignore | ||
.i18nrc.json | ||
.node-version | ||
.npmrc | ||
.nvmrc | ||
.prettierignore | ||
.prettierrc | ||
.stylelintignore | ||
.stylelintrc | ||
.telemetryrc.json | ||
.yarnrc | ||
BUILD.bazel | ||
CODE_OF_CONDUCT.md | ||
CONTRIBUTING.md | ||
FAQ.md | ||
fleet_packages.json | ||
github_checks_reporter.json | ||
Jenkinsfile | ||
kibana.d.ts | ||
LICENSE.txt | ||
nav-kibana-dev.docnav.json | ||
NOTICE.txt | ||
package.json | ||
preinstall_check.js | ||
README.md | ||
renovate.json | ||
RISK_MATRIX.mdx | ||
SECURITY.md | ||
STYLEGUIDE.mdx | ||
tsconfig.base.json | ||
tsconfig.bazel.json | ||
tsconfig.browser.json | ||
tsconfig.browser_bazel.json | ||
tsconfig.json | ||
tsconfig.types.json | ||
TYPESCRIPT.md | ||
versions.json | ||
WORKSPACE.bazel | ||
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.mdx.
- 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. | 7.15.1 | 7.15.1 | 💚 OK |
ES patch number is newer. | 7.15.0 | 7.15.1 | ⚠️ Logged warning |
ES minor number is newer. | 7.14.2 | 7.15.0 | ⚠️ Logged warning |
ES major number is newer. | 7.15.1 | 8.0.0 | 🚫 Fatal error |
ES patch number is older. | 7.15.1 | 7.15.0 | ⚠️ Logged warning |
ES minor number is older. | 7.15.1 | 7.14.2 | 🚫 Fatal error |
ES major number is older. | 8.0.0 | 7.15.1 | 🚫 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.