Your window into the Elastic Stack
Find a file
Kibana Machine 6593d2318f
[8.8] [Infrastructure UI] Hosts view handle invalid KQL error (#156989) (#157418)
# Backport

This will backport the following commits from `main` to `8.8`:
- [[Infrastructure UI] Hosts view handle invalid KQL error
(#156989)](https://github.com/elastic/kibana/pull/156989)

<!--- Backport version: 8.9.7 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Carlos
Crespo","email":"crespocarlos@users.noreply.github.com"},"sourceCommit":{"committedDate":"2023-05-11T16:59:23Z","message":"[Infrastructure
UI] Hosts view handle invalid KQL error (#156989)\n\ncloses
[#987](https://github.com/elastic/obs-infraobs-team/issues/987)\r\n\r\n##
Summary\r\n\r\nThis PR changes the hosts view to graciously handle
exceptions caused by\r\ninvalid KQL submissions\r\n\r\n<img
width=\"1451\"
alt=\"image\"\r\nsrc=\"5bafc987-9a14-4b03-9038-53179f7b6735\">\r\n\r\n\r\nBesides,
it changes the way it was handling a fatal error that can\r\nhappen if
something wrong happens while creating an ad-hoc data-view -\r\nthis is
highly unlike to happen, but we're standardizing how we
display\r\nerrors on the hosts view\r\n\r\n_Previously:_\r\n<img
width=\"1439\"
alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/2767137/236833673-c994512f-cb73-441b-9783-506bab67ff4b.png\">\r\n\r\n_Now:_\r\n<img
width=\"1439\"
alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/2767137/236862216-fada9f50-5d27-45b9-a6f3-8ac497a3e048.png\">\r\n\r\n###
How to test\r\n- Go to hosts view\r\n- Type invalid KQL expressions on
the search bar\r\n\r\n### For reviewer\r\n\r\nIf the page is loaded with
a querystring containing an invalid
`query`\r\n(e.g:\r\n`_a=(dateRange:(from:now-15m,to:now),filters:!(),limit:20,panelFilters:!(),query:(language:kuery,query:%27%7D%27)`),\r\nthe
Control components will show an error. However, they can't
recover\r\nfrom fatal errors. So even after the user corrects the
mistake in the\r\nquery, the controls will remain in the error
state.\r\n\r\nA ticket has been opened to address this
problem:\r\nhttps://github.com/elastic/kibana/issues/156430\r\n\r\n---------\r\n\r\nCo-authored-by:
Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"8baff25966d45c1b351e96a5cc524372b4dbdb29","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Metrics
UI","Team:Infra Monitoring
UI","release_note:skip","backport:prev-minor","Feature:ObsHosts","v8.9.0"],"number":156989,"url":"https://github.com/elastic/kibana/pull/156989","mergeCommit":{"message":"[Infrastructure
UI] Hosts view handle invalid KQL error (#156989)\n\ncloses
[#987](https://github.com/elastic/obs-infraobs-team/issues/987)\r\n\r\n##
Summary\r\n\r\nThis PR changes the hosts view to graciously handle
exceptions caused by\r\ninvalid KQL submissions\r\n\r\n<img
width=\"1451\"
alt=\"image\"\r\nsrc=\"5bafc987-9a14-4b03-9038-53179f7b6735\">\r\n\r\n\r\nBesides,
it changes the way it was handling a fatal error that can\r\nhappen if
something wrong happens while creating an ad-hoc data-view -\r\nthis is
highly unlike to happen, but we're standardizing how we
display\r\nerrors on the hosts view\r\n\r\n_Previously:_\r\n<img
width=\"1439\"
alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/2767137/236833673-c994512f-cb73-441b-9783-506bab67ff4b.png\">\r\n\r\n_Now:_\r\n<img
width=\"1439\"
alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/2767137/236862216-fada9f50-5d27-45b9-a6f3-8ac497a3e048.png\">\r\n\r\n###
How to test\r\n- Go to hosts view\r\n- Type invalid KQL expressions on
the search bar\r\n\r\n### For reviewer\r\n\r\nIf the page is loaded with
a querystring containing an invalid
`query`\r\n(e.g:\r\n`_a=(dateRange:(from:now-15m,to:now),filters:!(),limit:20,panelFilters:!(),query:(language:kuery,query:%27%7D%27)`),\r\nthe
Control components will show an error. However, they can't
recover\r\nfrom fatal errors. So even after the user corrects the
mistake in the\r\nquery, the controls will remain in the error
state.\r\n\r\nA ticket has been opened to address this
problem:\r\nhttps://github.com/elastic/kibana/issues/156430\r\n\r\n---------\r\n\r\nCo-authored-by:
Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"8baff25966d45c1b351e96a5cc524372b4dbdb29"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/156989","number":156989,"mergeCommit":{"message":"[Infrastructure
UI] Hosts view handle invalid KQL error (#156989)\n\ncloses
[#987](https://github.com/elastic/obs-infraobs-team/issues/987)\r\n\r\n##
Summary\r\n\r\nThis PR changes the hosts view to graciously handle
exceptions caused by\r\ninvalid KQL submissions\r\n\r\n<img
width=\"1451\"
alt=\"image\"\r\nsrc=\"5bafc987-9a14-4b03-9038-53179f7b6735\">\r\n\r\n\r\nBesides,
it changes the way it was handling a fatal error that can\r\nhappen if
something wrong happens while creating an ad-hoc data-view -\r\nthis is
highly unlike to happen, but we're standardizing how we
display\r\nerrors on the hosts view\r\n\r\n_Previously:_\r\n<img
width=\"1439\"
alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/2767137/236833673-c994512f-cb73-441b-9783-506bab67ff4b.png\">\r\n\r\n_Now:_\r\n<img
width=\"1439\"
alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/2767137/236862216-fada9f50-5d27-45b9-a6f3-8ac497a3e048.png\">\r\n\r\n###
How to test\r\n- Go to hosts view\r\n- Type invalid KQL expressions on
the search bar\r\n\r\n### For reviewer\r\n\r\nIf the page is loaded with
a querystring containing an invalid
`query`\r\n(e.g:\r\n`_a=(dateRange:(from:now-15m,to:now),filters:!(),limit:20,panelFilters:!(),query:(language:kuery,query:%27%7D%27)`),\r\nthe
Control components will show an error. However, they can't
recover\r\nfrom fatal errors. So even after the user corrects the
mistake in the\r\nquery, the controls will remain in the error
state.\r\n\r\nA ticket has been opened to address this
problem:\r\nhttps://github.com/elastic/kibana/issues/156430\r\n\r\n---------\r\n\r\nCo-authored-by:
Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"8baff25966d45c1b351e96a5cc524372b4dbdb29"}}]}]
BACKPORT-->

Co-authored-by: Carlos Crespo <crespocarlos@users.noreply.github.com>
2023-05-11 11:08:49 -07:00
.buildkite [8.8] [functional tests] split fleet_api_integration config into smaller ones (#156407) (#156559) 2023-05-03 08:33:03 -07:00
.ci Upgrade Node.js to 16.19.1 (#151527) 2023-02-21 10:40:59 -06:00
.github chore(NA): remove codeowners and update branch property after branch cut 2023-04-26 16:24:35 +01:00
api_docs [api-docs] 2023-04-26 Daily api_docs build (#155820) 2023-04-26 00:59:36 -04:00
config [8.8] [Serverless] Select project type via config (#155754) (#155997) 2023-04-27 08:19:35 -07:00
dev_docs [8.8] [performance] enable journey run against cloud deployments (#156720) (#157123) 2023-05-08 21:46:16 -07:00
docs [8.8] [DOCS] Adds 8.8.0 release notes (#155951) (#157420) 2023-05-11 13:36:27 -04:00
examples [8.8] [Search Sessions] Fix flaky partial results test in search examples (#155816) (#156125) 2023-04-27 17:34:02 -07:00
kbn_pm chore(NA): exit early with link for docs when using kbn_pm on windows (#139745) 2023-02-10 15:38:29 +00:00
legacy_rfcs rename @elastic/* packages to @kbn/* (#138957) 2022-08-18 08:54:42 -07:00
licenses Elastic License 2.0 (#90099) 2021-02-03 18:12:39 -08:00
packages [8.8] Fix the charts and group by section on the Log Threshold alert detail page (#155327) (#157410) 2023-05-11 10:03:34 -07:00
plugins
scripts [ci] build next docs in PRs when relevant files change (#149991) 2023-02-09 21:57:10 -07:00
src [8.8] [Discover] Fix filtering with date_nanos type and negating (#156103) (#157319) 2023-05-10 13:57:45 -07:00
test [8.8] Update ftr services to handle occasional WebDriverError (#157283) (#157326) 2023-05-10 13:50:57 -07:00
typings Wrap rison-node to improve types (#146649) 2022-12-01 08:33:56 -07:00
vars [ts] ts refs cache was removed, remove capture task 2022-10-28 14:27:18 -05:00
x-pack [8.8] [Infrastructure UI] Hosts view handle invalid KQL error (#156989) (#157418) 2023-05-11 11:08:49 -07:00
.backportrc.json chore(NA): adds 8.7 into backportrc (#150569) 2023-02-08 21:22:43 +00:00
.bazelignore Bazel config maintenance (#135442) 2022-07-05 10:20:26 -05:00
.bazeliskversion chore(NA): upgrade bazelisk into v1.11.0 (#125070) 2022-02-09 20:43:57 +00:00
.bazelrc chore(NA): use new and more performant BuildBuddy servers (#130350) 2022-04-18 02:01:38 +01:00
.bazelrc.common Transpile packages on demand, validate all TS projects (#146212) 2022-12-22 19:00:29 -06:00
.bazelversion chore(NA): revert bazel upgrade for v5.2.0 (#135096) 2022-06-24 03:57:21 +01:00
.browserslistrc [browserslist] remove unnecessary browsers (#89186) 2021-01-25 16:30:18 -07:00
.editorconfig .editorconfig MDX files should follow the same rules as MD (#96942) 2021-04-13 11:40:42 -04:00
.eslintignore [NOTICE.txt] Fix notices for Gainsight and FullStory (#146004) 2023-01-13 14:49:43 +01:00
.eslintrc.js [SecuritySolution] Refactor security packages (#155365) 2023-04-26 05:05:36 -07:00
.gitattributes
.gitignore [packages] migrate all plugins to packages (#148130) 2023-02-08 21:06:50 -06:00
.i18nrc.json [SecuritySolution] Refactor security packages (#155365) 2023-04-26 05:05:36 -07:00
.node-version Upgrade Node.js to 16.19.1 (#151527) 2023-02-21 10:40:59 -06:00
.npmrc
.nvmrc Upgrade Node.js to 16.19.1 (#151527) 2023-02-21 10:40:59 -06:00
.prettierignore [dev] Replace sass-lint with stylelint (#86177) 2021-01-15 11:52:29 -06:00
.prettierrc
.stylelintignore chore(NA): stop grouping bazel out symlink folders (#96066) 2021-04-01 14:16:14 -05:00
.stylelintrc Bump stylelint to ^14 (#136693) 2022-07-20 10:11:00 -05:00
.telemetryrc.json [Telemetry] Fix telemetry-tools TS parser for packages (#149819) 2023-01-31 04:09:09 +03:00
.yarnrc chore(NA): manage npm dependencies within bazel (#92864) 2021-03-03 12:37:20 -05:00
BUILD.bazel Transpile packages on demand, validate all TS projects (#146212) 2022-12-22 19:00:29 -06:00
CODE_OF_CONDUCT.md Add CODE_OF_CONDUCT.md (#87439) 2021-02-23 09:01:51 +01:00
CONTRIBUTING.md Update doc slugs to improve analytic tracking, move to appropriate folders (#113630) 2021-10-04 13:36:45 -04:00
FAQ.md Fix small typos in the root md files (#134609) 2022-06-23 09:36:11 -05:00
fleet_packages.json [8.8] Sync bundled packages with Package Storage (#157305) 2023-05-10 12:14:18 -07:00
github_checks_reporter.json
Jenkinsfile [CI] Disable tracked branch jobs in Jenkins, enable reporting in Buildkite (#112604) 2021-09-21 11:31:15 -04:00
kibana.d.ts fix all violations 2022-04-16 01:37:30 -05:00
LICENSE.txt Elastic License 2.0 (#90099) 2021-02-03 18:12:39 -08:00
nav-kibana-dev.docnav.json Add March 2023 Newsletter link (#154248) 2023-04-06 16:04:06 -04:00
NOTICE.txt [FullStory] Update snippet (#153570) 2023-04-18 04:06:05 -07:00
package.json [8.8] [Enterprise Search] update search-ui + remove searchable-fields config (#157209) (#157244) 2023-05-10 02:52:58 -07:00
preinstall_check.js Elastic License 2.0 (#90099) 2021-02-03 18:12:39 -08:00
README.md [README] Update version Compatibility with Elasticsearch (#116040) 2022-01-10 10:31:21 -05:00
renovate.json Session view and k8s dashboard fixes (#154982) 2023-04-17 16:22:28 -07:00
RISK_MATRIX.mdx Add "Risk Matrix" section to the PR template (#100649) 2021-06-02 14:43:47 +02:00
SECURITY.md
STYLEGUIDE.mdx [styleguide] update path to scss theme (#140742) 2022-09-15 10:41:14 -04:00
tsconfig.base.json [SecuritySolution] Refactor security packages (#155365) 2023-04-26 05:05:36 -07:00
tsconfig.browser.json
tsconfig.browser_bazel.json [build_ts_refs] improve caches, allow building a subset of projects (#107981) 2021-08-10 22:12:45 -07:00
tsconfig.json Transpile packages on demand, validate all TS projects (#146212) 2022-12-22 19:00:29 -06:00
TYPESCRIPT.md Fix small typos in the root md files (#134609) 2022-06-23 09:36:11 -05:00
versions.json chore(NA): update versions after v8.7.1 bump (#154029) 2023-03-30 16:11:53 +01:00
WORKSPACE.bazel Upgrade Node.js to 16.19.1 (#151527) 2023-02-21 10:40:59 -06:00
yarn.lock [8.8] [Enterprise Search] update search-ui + remove searchable-fields config (#157209) (#157244) 2023-05-10 02:52:58 -07: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. 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.