github-mirrors/kibana
1
0
Fork 0
mirror of https://github.com/elastic/kibana.git synced 2025-04-24 09:48:58 -04:00
Code Issues Projects Releases Packages Wiki Activity
Your window into the Elastic Stack
82370 commits 428 branches 496 tags 23 GiB
Find a file
Kibana Machine 2046aed6a6
[8.x] [scout] unique runId for reporting, disabled failed test reporter locally (#209507) (#210088) 
# Backport

This will backport the following commits from `main` to `8.x`:
- [[scout] unique runId for reporting, disabled failed test reporter
locally (#209507)](https://github.com/elastic/kibana/pull/209507)

<!--- Backport version: 9.4.3 -->

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

<!--BACKPORT [{"author":{"name":"Dzmitry
Lemechko","email":"dzmitry.lemechko@elastic.co"},"sourceCommit":{"committedDate":"2025-02-05T15:35:26Z","message":"[scout]
unique runId for reporting, disabled failed test reporter locally
(#209507)\n\n## Summary\r\n\r\nThis PR makes few changes to scout
reporter:\r\n\r\nRecently I found out that Playwright load configuration
file _multiple\r\ntimes_:\r\n- first time after you run `npx playwright
test -c ...`\r\n- on every worker start\r\n\r\nlog
before:\r\n\r\n```\r\n[main][~/github/kibana]$ npx playwright test
--config
x-pack/platform/plugins/shared/maps/ui_tests/playwright.config.ts\r\n[createPlaywrightConfig]
called with runId: 18f35f735a10155c\r\n\r\nRunning 1 test using 1
worker\r\n\r\n[createPlaywrightConfig] called with runId:
2633b4e4c20afa15\r\n[chromium] › full_screen_mode.spec.ts:28:9 › Maps ›
Full screen mode @svlSecurity @svlOblt @svlSearch
@ess\r\n```\r\n\r\nWith our current logic unique `runId` will be
generated on each\r\nconfiguration load, meaning for parallel run we
will report failures in\r\ndifferent directories instead of the same
one.\r\n\r\nPlaywright doesn't expose any unique identifier for the run,
so we have\r\ndo something similar described
in\r\n\r\nhttps://github.com/microsoft/playwright/issues/28941#issuecomment-1888008102\r\n\r\nlog
after fix:\r\n\r\n```\r\n[main][~/github/kibana]$ npx playwright test
--config
x-pack/platform/plugins/shared/maps/ui_tests/playwright.config.ts\r\n[createPlaywrightConfig]
called with runId: 310a576f32d3b8a5\r\n\r\nRunning 1 test using 1
worker\r\n\r\n[createPlaywrightConfig] called with runId:
310a576f32d3b8a5\r\n[chromium] › full_screen_mode.spec.ts:28:9 › Maps ›
Full screen mode @svlSecurity @svlOblt @svlSearch @ess\r\n```\r\n\r\nWe
also had a chat with @dolaru and agreed that Scout reporters to
be\r\ndisabled for local test run. Few reasons:\r\n- Scout custom
reporting targets CI execution: events-based reporter was\r\nalready
disabled\r\n- Failed test reporter purpose is to provide html
boilerplate to be\r\nannotated in pipeline build\r\n- When you run tests
with IDE playwright plugin it provides its own\r\nreporter / history,
should be
enough.","sha":"6635fe501c307d567afa71a346fc91a7675e3cc5","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:prev-minor","backport:prev-major","test:scout","v9.1.0"],"title":"[scout]
unique runId for reporting, disabled failed test reporter
locally","number":209507,"url":"https://github.com/elastic/kibana/pull/209507","mergeCommit":{"message":"[scout]
unique runId for reporting, disabled failed test reporter locally
(#209507)\n\n## Summary\r\n\r\nThis PR makes few changes to scout
reporter:\r\n\r\nRecently I found out that Playwright load configuration
file _multiple\r\ntimes_:\r\n- first time after you run `npx playwright
test -c ...`\r\n- on every worker start\r\n\r\nlog
before:\r\n\r\n```\r\n[main][~/github/kibana]$ npx playwright test
--config
x-pack/platform/plugins/shared/maps/ui_tests/playwright.config.ts\r\n[createPlaywrightConfig]
called with runId: 18f35f735a10155c\r\n\r\nRunning 1 test using 1
worker\r\n\r\n[createPlaywrightConfig] called with runId:
2633b4e4c20afa15\r\n[chromium] › full_screen_mode.spec.ts:28:9 › Maps ›
Full screen mode @svlSecurity @svlOblt @svlSearch
@ess\r\n```\r\n\r\nWith our current logic unique `runId` will be
generated on each\r\nconfiguration load, meaning for parallel run we
will report failures in\r\ndifferent directories instead of the same
one.\r\n\r\nPlaywright doesn't expose any unique identifier for the run,
so we have\r\ndo something similar described
in\r\n\r\nhttps://github.com/microsoft/playwright/issues/28941#issuecomment-1888008102\r\n\r\nlog
after fix:\r\n\r\n```\r\n[main][~/github/kibana]$ npx playwright test
--config
x-pack/platform/plugins/shared/maps/ui_tests/playwright.config.ts\r\n[createPlaywrightConfig]
called with runId: 310a576f32d3b8a5\r\n\r\nRunning 1 test using 1
worker\r\n\r\n[createPlaywrightConfig] called with runId:
310a576f32d3b8a5\r\n[chromium] › full_screen_mode.spec.ts:28:9 › Maps ›
Full screen mode @svlSecurity @svlOblt @svlSearch @ess\r\n```\r\n\r\nWe
also had a chat with @dolaru and agreed that Scout reporters to
be\r\ndisabled for local test run. Few reasons:\r\n- Scout custom
reporting targets CI execution: events-based reporter was\r\nalready
disabled\r\n- Failed test reporter purpose is to provide html
boilerplate to be\r\nannotated in pipeline build\r\n- When you run tests
with IDE playwright plugin it provides its own\r\nreporter / history,
should be
enough.","sha":"6635fe501c307d567afa71a346fc91a7675e3cc5"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/209808","number":209808,"state":"MERGED","mergeCommit":{"sha":"2c04505bd6ad9db59e0ea3aa617d649b41134294","message":"[9.0]
[scout] unique runId for reporting, disabled failed test reporter
locally (#209507) (#209808)\n\n# Backport\n\nThis will backport the
following commits from `main` to `9.0`:\n- [[scout] unique runId for
reporting, disabled failed test reporter\nlocally
(#209507)](https://github.com/elastic/kibana/pull/209507)\n\n<!---
Backport version: 9.4.3 -->\n\n### Questions ?\nPlease refer to the
[Backport
tool\ndocumentation](https://github.com/sqren/backport)\n\n<!--BACKPORT
[{\"author\":{\"name\":\"Dzmitry\nLemechko\",\"email\":\"dzmitry.lemechko@elastic.co\"},\"sourceCommit\":{\"committedDate\":\"2025-02-05T15:35:26Z\",\"message\":\"[scout]\nunique
runId for reporting, disabled failed test reporter
locally\n(#209507)\\n\\n## Summary\\r\\n\\r\\nThis PR makes few changes
to scout\nreporter:\\r\\n\\r\\nRecently I found out that Playwright load
configuration\nfile _multiple\\r\\ntimes_:\\r\\n- first time after you
run `npx playwright\ntest -c ...`\\r\\n- on every worker
start\\r\\n\\r\\nlog\nbefore:\\r\\n\\r\\n```\\r\\n[main][~/github/kibana]$
npx playwright
test\n--config\nx-pack/platform/plugins/shared/maps/ui_tests/playwright.config.ts\\r\\n[createPlaywrightConfig]\ncalled
with runId: 18f35f735a10155c\\r\\n\\r\\nRunning 1 test using
1\nworker\\r\\n\\r\\n[createPlaywrightConfig] called with
runId:\n2633b4e4c20afa15\\r\\n[chromium] › full_screen_mode.spec.ts:28:9
› Maps ›\nFull screen mode @svlSecurity @svlOblt
@svlSearch\n@ess\\r\\n```\\r\\n\\r\\nWith our current logic unique
`runId` will be\ngenerated on each\\r\\nconfiguration load, meaning for
parallel run we\nwill report failures in\\r\\ndifferent directories
instead of the same\none.\\r\\n\\r\\nPlaywright doesn't expose any
unique identifier for the run,\nso we have\\r\\ndo something similar
described\nin\\r\\n\\r\\nhttps://github.com/microsoft/playwright/issues/28941#issuecomment-1888008102\\r\\n\\r\\nlog\nafter
fix:\\r\\n\\r\\n```\\r\\n[main][~/github/kibana]$ npx playwright
test\n--config\nx-pack/platform/plugins/shared/maps/ui_tests/playwright.config.ts\\r\\n[createPlaywrightConfig]\ncalled
with runId: 310a576f32d3b8a5\\r\\n\\r\\nRunning 1 test using
1\nworker\\r\\n\\r\\n[createPlaywrightConfig] called with
runId:\n310a576f32d3b8a5\\r\\n[chromium] › full_screen_mode.spec.ts:28:9
› Maps ›\nFull screen mode @svlSecurity @svlOblt @svlSearch
@ess\\r\\n```\\r\\n\\r\\nWe\nalso had a chat with @dolaru and agreed
that Scout reporters to\nbe\\r\\ndisabled for local test run. Few
reasons:\\r\\n- Scout custom\nreporting targets CI execution:
events-based reporter was\\r\\nalready\ndisabled\\r\\n- Failed test
reporter purpose is to provide html\nboilerplate to be\\r\\nannotated in
pipeline build\\r\\n- When you run tests\nwith IDE playwright plugin it
provides its own\\r\\nreporter / history,\nshould
be\nenough.\",\"sha\":\"6635fe501c307d567afa71a346fc91a7675e3cc5\",\"branchLabelMapping\":{\"^v9.1.0$\":\"main\",\"^v8.19.0$\":\"8.x\",\"^v(\\\\d+).(\\\\d+).\\\\d+$\":\"$1.$2\"}},\"sourcePullRequest\":{\"labels\":[\"release_note:skip\",\"v9.0.0\",\"backport:prev-minor\",\"test:scout\",\"v9.1.0\"],\"title\":\"[scout]\nunique
runId for reporting, disabled failed test
reporter\nlocally\",\"number\":209507,\"url\":\"https://github.com/elastic/kibana/pull/209507\",\"mergeCommit\":{\"message\":\"[scout]\nunique
runId for reporting, disabled failed test reporter
locally\n(#209507)\\n\\n## Summary\\r\\n\\r\\nThis PR makes few changes
to scout\nreporter:\\r\\n\\r\\nRecently I found out that Playwright load
configuration\nfile _multiple\\r\\ntimes_:\\r\\n- first time after you
run `npx playwright\ntest -c ...`\\r\\n- on every worker
start\\r\\n\\r\\nlog\nbefore:\\r\\n\\r\\n```\\r\\n[main][~/github/kibana]$
npx playwright
test\n--config\nx-pack/platform/plugins/shared/maps/ui_tests/playwright.config.ts\\r\\n[createPlaywrightConfig]\ncalled
with runId: 18f35f735a10155c\\r\\n\\r\\nRunning 1 test using
1\nworker\\r\\n\\r\\n[createPlaywrightConfig] called with
runId:\n2633b4e4c20afa15\\r\\n[chromium] › full_screen_mode.spec.ts:28:9
› Maps ›\nFull screen mode @svlSecurity @svlOblt
@svlSearch\n@ess\\r\\n```\\r\\n\\r\\nWith our current logic unique
`runId` will be\ngenerated on each\\r\\nconfiguration load, meaning for
parallel run we\nwill report failures in\\r\\ndifferent directories
instead of the same\none.\\r\\n\\r\\nPlaywright doesn't expose any
unique identifier for the run,\nso we have\\r\\ndo something similar
described\nin\\r\\n\\r\\nhttps://github.com/microsoft/playwright/issues/28941#issuecomment-1888008102\\r\\n\\r\\nlog\nafter
fix:\\r\\n\\r\\n```\\r\\n[main][~/github/kibana]$ npx playwright
test\n--config\nx-pack/platform/plugins/shared/maps/ui_tests/playwright.config.ts\\r\\n[createPlaywrightConfig]\ncalled
with runId: 310a576f32d3b8a5\\r\\n\\r\\nRunning 1 test using
1\nworker\\r\\n\\r\\n[createPlaywrightConfig] called with
runId:\n310a576f32d3b8a5\\r\\n[chromium] › full_screen_mode.spec.ts:28:9
› Maps ›\nFull screen mode @svlSecurity @svlOblt @svlSearch
@ess\\r\\n```\\r\\n\\r\\nWe\nalso had a chat with @dolaru and agreed
that Scout reporters to\nbe\\r\\ndisabled for local test run. Few
reasons:\\r\\n- Scout custom\nreporting targets CI execution:
events-based reporter was\\r\\nalready\ndisabled\\r\\n- Failed test
reporter purpose is to provide html\nboilerplate to be\\r\\nannotated in
pipeline build\\r\\n- When you run tests\nwith IDE playwright plugin it
provides its own\\r\\nreporter / history,\nshould
be\nenough.\",\"sha\":\"6635fe501c307d567afa71a346fc91a7675e3cc5\"}},\"sourceBranch\":\"main\",\"suggestedTargetBranches\":[\"9.0\"],\"targetPullRequestStates\":[{\"branch\":\"9.0\",\"label\":\"v9.0.0\",\"branchLabelMappingKey\":\"^v(\\\\d+).(\\\\d+).\\\\d+$\",\"isSourceBranch\":false,\"state\":\"NOT_CREATED\"},{\"branch\":\"main\",\"label\":\"v9.1.0\",\"branchLabelMappingKey\":\"^v9.1.0$\",\"isSourceBranch\":true,\"state\":\"MERGED\",\"url\":\"https://github.com/elastic/kibana/pull/209507\",\"number\":209507,\"mergeCommit\":{\"message\":\"[scout]\nunique
runId for reporting, disabled failed test reporter
locally\n(#209507)\\n\\n## Summary\\r\\n\\r\\nThis PR makes few changes
to scout\nreporter:\\r\\n\\r\\nRecently I found out that Playwright load
configuration\nfile _multiple\\r\\ntimes_:\\r\\n- first time after you
run `npx playwright\ntest -c ...`\\r\\n- on every worker
start\\r\\n\\r\\nlog\nbefore:\\r\\n\\r\\n```\\r\\n[main][~/github/kibana]$
npx playwright
test\n--config\nx-pack/platform/plugins/shared/maps/ui_tests/playwright.config.ts\\r\\n[createPlaywrightConfig]\ncalled
with runId: 18f35f735a10155c\\r\\n\\r\\nRunning 1 test using
1\nworker\\r\\n\\r\\n[createPlaywrightConfig] called with
runId:\n2633b4e4c20afa15\\r\\n[chromium] › full_screen_mode.spec.ts:28:9
› Maps ›\nFull screen mode @svlSecurity @svlOblt
@svlSearch\n@ess\\r\\n```\\r\\n\\r\\nWith our current logic unique
`runId` will be\ngenerated on each\\r\\nconfiguration load, meaning for
parallel run we\nwill report failures in\\r\\ndifferent directories
instead of the same\none.\\r\\n\\r\\nPlaywright doesn't expose any
unique identifier for the run,\nso we have\\r\\ndo something similar
described\nin\\r\\n\\r\\nhttps://github.com/microsoft/playwright/issues/28941#issuecomment-1888008102\\r\\n\\r\\nlog\nafter
fix:\\r\\n\\r\\n```\\r\\n[main][~/github/kibana]$ npx playwright
test\n--config\nx-pack/platform/plugins/shared/maps/ui_tests/playwright.config.ts\\r\\n[createPlaywrightConfig]\ncalled
with runId: 310a576f32d3b8a5\\r\\n\\r\\nRunning 1 test using
1\nworker\\r\\n\\r\\n[createPlaywrightConfig] called with
runId:\n310a576f32d3b8a5\\r\\n[chromium] › full_screen_mode.spec.ts:28:9
› Maps ›\nFull screen mode @svlSecurity @svlOblt @svlSearch
@ess\\r\\n```\\r\\n\\r\\nWe\nalso had a chat with @dolaru and agreed
that Scout reporters to\nbe\\r\\ndisabled for local test run. Few
reasons:\\r\\n- Scout custom\nreporting targets CI execution:
events-based reporter was\\r\\nalready\ndisabled\\r\\n- Failed test
reporter purpose is to provide html\nboilerplate to be\\r\\nannotated in
pipeline build\\r\\n- When you run tests\nwith IDE playwright plugin it
provides its own\\r\\nreporter / history,\nshould be
enough.\",\"sha\":\"6635fe501c307d567afa71a346fc91a7675e3cc5\"}}]}]\nBACKPORT-->\n\nCo-authored-by:
Dzmitry Lemechko
<dzmitry.lemechko@elastic.co>"}},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/209507","number":209507,"mergeCommit":{"message":"[scout]
unique runId for reporting, disabled failed test reporter locally
(#209507)\n\n## Summary\r\n\r\nThis PR makes few changes to scout
reporter:\r\n\r\nRecently I found out that Playwright load configuration
file _multiple\r\ntimes_:\r\n- first time after you run `npx playwright
test -c ...`\r\n- on every worker start\r\n\r\nlog
before:\r\n\r\n```\r\n[main][~/github/kibana]$ npx playwright test
--config
x-pack/platform/plugins/shared/maps/ui_tests/playwright.config.ts\r\n[createPlaywrightConfig]
called with runId: 18f35f735a10155c\r\n\r\nRunning 1 test using 1
worker\r\n\r\n[createPlaywrightConfig] called with runId:
2633b4e4c20afa15\r\n[chromium] › full_screen_mode.spec.ts:28:9 › Maps ›
Full screen mode @svlSecurity @svlOblt @svlSearch
@ess\r\n```\r\n\r\nWith our current logic unique `runId` will be
generated on each\r\nconfiguration load, meaning for parallel run we
will report failures in\r\ndifferent directories instead of the same
one.\r\n\r\nPlaywright doesn't expose any unique identifier for the run,
so we have\r\ndo something similar described
in\r\n\r\nhttps://github.com/microsoft/playwright/issues/28941#issuecomment-1888008102\r\n\r\nlog
after fix:\r\n\r\n```\r\n[main][~/github/kibana]$ npx playwright test
--config
x-pack/platform/plugins/shared/maps/ui_tests/playwright.config.ts\r\n[createPlaywrightConfig]
called with runId: 310a576f32d3b8a5\r\n\r\nRunning 1 test using 1
worker\r\n\r\n[createPlaywrightConfig] called with runId:
310a576f32d3b8a5\r\n[chromium] › full_screen_mode.spec.ts:28:9 › Maps ›
Full screen mode @svlSecurity @svlOblt @svlSearch @ess\r\n```\r\n\r\nWe
also had a chat with @dolaru and agreed that Scout reporters to
be\r\ndisabled for local test run. Few reasons:\r\n- Scout custom
reporting targets CI execution: events-based reporter was\r\nalready
disabled\r\n- Failed test reporter purpose is to provide html
boilerplate to be\r\nannotated in pipeline build\r\n- When you run tests
with IDE playwright plugin it provides its own\r\nreporter / history,
should be enough.","sha":"6635fe501c307d567afa71a346fc91a7675e3cc5"}}]}]
BACKPORT-->

Co-authored-by: Dzmitry Lemechko <dzmitry.lemechko@elastic.co>
2025-02-09 13:14:39 +01:00
.buildkite [8.x] [Console] Fix typo in generated PR title (#209255) (#209464) 2025-02-04 11:06:38 +01:00
.devcontainer [8.x] Sync devcontainer with main (#202854) 2024-12-03 17:10:40 -08:00
.github [8.x] Introduce the InferenceChatModel for langchain (#206429) (#209277) 2025-02-03 16:32:00 +01:00
api_docs [8.x] [Streams 🌊] Introduce GroupStreams (#208126) (#209871) 2025-02-06 14:09:59 +01:00
config [8.x] [Inference Connector] Enable inference connector for ESS by default, disable it for Serverless (#209197) (#209865) 2025-02-06 17:17:01 +01:00
dev_docs [8.x] [Hardening] Kibana Feature API Privileges Names (#208067) (#209321) 2025-02-03 11:51:36 -05:00
docs [Docs] 8.16.4 release notes (#210108) 2025-02-07 19:18:01 +00:00
examples [8.x] [Embeddable] EUI Visual Refresh Integration (#204452) (#208565) 2025-01-29 14:47:30 -05:00
kbn_pm [8.x] Sustainable Kibana Architecture: Move CodeEditor related packages #205587 (#205738) (#205919) 2025-01-10 11:20:26 +00:00
legacy_rfcs [8.x] SKA: Update broken references and URLs (#206836) (#208479) 2025-01-28 10:09:09 +01:00
licenses Adds AGPL 3.0 license (#192025) 2024-09-06 19:02:41 -06:00
oas_docs [8.x] [SecuritySolution][Endpoint] Update request docs for isolate/release/processes (#209097) (#210162) 2025-02-07 17:32:18 +01:00
packages [8.x] [scout] unique runId for reporting, disabled failed test reporter locally (#209507) (#210088) 2025-02-09 13:14:39 +01:00
plugins
scripts [8.x] SKA: Update broken references and URLs (#206836) (#208479) 2025-01-28 10:09:09 +01:00
src [8.x] ESQL: Add reference entry for LOOKUP JOIN (#210201) (#210267) 2025-02-07 23:27:22 +01:00
test [8.x] [Dashboard] Presentation panel refactor (#207275) (#210030) 2025-02-06 14:59:26 -07:00
typings [8.x] make emotion typing global (#200958) (#203162) 2024-12-05 14:10:16 -06:00
x-pack [8.x] fix: [Security:Manage:EntityAnalytics:EntityRiskScore] Entity Risk score on and off toggle button is missing discernible text on Entity Risk score page (#207362) (#210148) 2025-02-08 10:46:13 +01:00
.backportrc.json chore(NA): adds 8.16 into backportrc (#187530) 2024-07-04 19:09:25 +01:00
.bazelignore Remove references to deleted .ci folder (#177168) 2024-02-20 19:54:21 +01: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 Add Firefox ESR to browserlistrc (#184462) 2024-05-29 17:53:18 -05:00
.editorconfig
.eslintignore [8.x] SKA: Fix outdated eslint rules (#206961) (#208486) 2025-01-28 14:46:39 +01:00
.eslintrc.js [8.x] SKA: Update repository structure documentation (#208691) (#208831) 2025-01-30 12:40:53 +03:00
.gitattributes
.gitignore [8.x] Sustainable Kibana Architecture: Move modules owned by @elastic/kibana-operations (#202739) (#205320) 2024-12-31 19:01:38 +01:00
.i18nrc.json [8.x] [Discover] In-table search (#206454) (#208868) 2025-01-30 09:16:33 +01:00
.node-version [8.x] Upgrade Node.js to 20.18.2 (#207431) (#207894) 2025-01-22 19:37:48 +00:00
.npmrc [npmrc] Fix puppeteer_skip_download configuration (#177673) 2024-02-22 18:59:01 -07:00
.nvmrc [8.x] Upgrade Node.js to 20.18.2 (#207431) (#207894) 2025-01-22 19:37:48 +00:00
.prettierignore
.prettierrc
.puppeteerrc Add .puppeteerrc (#179847) 2024-04-03 09:14:39 -05:00
.stylelintignore
.stylelintrc Bump stylelint to ^14 (#136693) 2022-07-20 10:11:00 -05:00
.telemetryrc.json [8.x] Sustainable Kibana Architecture: Move modules owned by @elastic/kibana-core (#201653) (#205563) 2025-01-05 16:32:00 +01:00
.yarnrc
BUILD.bazel Transpile packages on demand, validate all TS projects (#146212) 2022-12-22 19:00:29 -06:00
catalog-info.yaml [sonarqube] Disable cron (#190611) 2024-08-15 09:19:09 -05:00
CODE_OF_CONDUCT.md
CONTRIBUTING.md
FAQ.md Fix small typos in the root md files (#134609) 2022-06-23 09:36:11 -05:00
fleet_packages.json [8.x] Sync bundled packages with Package Storage (#208241) 2025-01-27 13:05:25 +01:00
github_checks_reporter.json
kibana.d.ts Adds AGPL 3.0 license (#192025) 2024-09-06 19:02:41 -06:00
LICENSE.txt Adds AGPL 3.0 license (#192025) 2024-09-06 19:02:41 -06:00
NOTICE.txt [8.x] [ES|QL] capitalize &#x60;FROM&#x60; in recommended queries (#205122) (#205352) 2025-01-02 04:27:03 -06:00
package.json [8.x] Update dependency @types/diff to ^7.0.1 (main) (#210138) (#210280) 2025-02-08 00:28:19 +01:00
preinstall_check.js Adds AGPL 3.0 license (#192025) 2024-09-06 19:02:41 -06:00
README.md
renovate.json [8.x] [Renovate/Core] Use prev-minor backport strategy (#204709) (#204909) 2024-12-19 11:00:04 +00:00
RISK_MATRIX.mdx
run_fleet_setup_parallel.sh [8.x] Sustainable Kibana Architecture: Move modules owned by @elastic/fleet (#202422) (#205145) 2024-12-24 15:17:23 -06:00
SECURITY.md
sonar-project.properties [sonarqube] update memory, cpu (#190547) 2024-09-09 16:16:30 -05:00
STYLEGUIDE.mdx [styleguide] update path to scss theme (#140742) 2022-09-15 10:41:14 -04:00
tsconfig.base.json [8.x] Introduce the InferenceChatModel for langchain (#206429) (#209277) 2025-02-03 16:32:00 +01:00
tsconfig.browser.json
tsconfig.browser_bazel.json
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 [ci] Update version tracking for 7.17.25 (#192477) 2024-09-10 20:54:04 -05:00
WORKSPACE.bazel [8.x] Upgrade Node.js to 20.18.2 (#207431) (#207894) 2025-01-22 19:37:48 +00:00
yarn.lock [8.x] Update dependency @types/diff to ^7.0.1 (main) (#210138) (#210280) 2025-02-08 00:28:19 +01:00

README.md

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.