mirror of
https://github.com/elastic/kibana.git
synced 2025-04-24 17:59:23 -04:00
Your window into the Elastic Stack
b9fce2f5fc
# Backport This will backport the following commits from `main` to `8.x`: - [[Rule Migration] Improve rule translation prompts and processes (#204021)](https://github.com/elastic/kibana/pull/204021) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Marius Iversen","email":"marius.iversen@elastic.co"},"sourceCommit":{"committedDate":"2024-12-12T18:32:04Z","message":"[Rule Migration] Improve rule translation prompts and processes (#204021)\n\n## Summary\n\nThis PR performs multiple changes that all focuses on improving the\nquality of the results returned when we translate rules that do not\nmatch with a prebuilt rule and both with/without related integrations.\n\nChanges include:\n\n- Add a filter_index_patterns node, to always ensure `logs-*` is removed\nwith our `[indexPattern:logs-*]` value, which is similar to how we\ndetect missing lookups and macros.\n- Split `translate_rule` into another `ecs_mapping` node, trying to\nensure translation focuses on changing SPL to ESQL without any focus on\nactual field names, while the other node focuses only on the ESQL query\nand changing field names.\n- The summary now added in the comments have 1 for the translation and\none for the ECS mapping.\n- Add default rule batch size `15` with PR comment/question.\n- Ensure we only return one integration related rather than an array for\nnow, to make ESQL more focused on one related integration.\n- New prompt to filter out one or more integrations from the returned\nRAG; similar to how its done for rules RAG results already.","sha":"0a7262d0fc213148fd7e80d3dc65f79c7eeae244","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team: SecuritySolution","backport:prev-minor","v8.18.0"],"title":"[Rule Migration] Improve rule translation prompts and processes","number":204021,"url":"https://github.com/elastic/kibana/pull/204021","mergeCommit":{"message":"[Rule Migration] Improve rule translation prompts and processes (#204021)\n\n## Summary\n\nThis PR performs multiple changes that all focuses on improving the\nquality of the results returned when we translate rules that do not\nmatch with a prebuilt rule and both with/without related integrations.\n\nChanges include:\n\n- Add a filter_index_patterns node, to always ensure `logs-*` is removed\nwith our `[indexPattern:logs-*]` value, which is similar to how we\ndetect missing lookups and macros.\n- Split `translate_rule` into another `ecs_mapping` node, trying to\nensure translation focuses on changing SPL to ESQL without any focus on\nactual field names, while the other node focuses only on the ESQL query\nand changing field names.\n- The summary now added in the comments have 1 for the translation and\none for the ECS mapping.\n- Add default rule batch size `15` with PR comment/question.\n- Ensure we only return one integration related rather than an array for\nnow, to make ESQL more focused on one related integration.\n- New prompt to filter out one or more integrations from the returned\nRAG; similar to how its done for rules RAG results already.","sha":"0a7262d0fc213148fd7e80d3dc65f79c7eeae244"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/204021","number":204021,"mergeCommit":{"message":"[Rule Migration] Improve rule translation prompts and processes (#204021)\n\n## Summary\n\nThis PR performs multiple changes that all focuses on improving the\nquality of the results returned when we translate rules that do not\nmatch with a prebuilt rule and both with/without related integrations.\n\nChanges include:\n\n- Add a filter_index_patterns node, to always ensure `logs-*` is removed\nwith our `[indexPattern:logs-*]` value, which is similar to how we\ndetect missing lookups and macros.\n- Split `translate_rule` into another `ecs_mapping` node, trying to\nensure translation focuses on changing SPL to ESQL without any focus on\nactual field names, while the other node focuses only on the ESQL query\nand changing field names.\n- The summary now added in the comments have 1 for the translation and\none for the ECS mapping.\n- Add default rule batch size `15` with PR comment/question.\n- Ensure we only return one integration related rather than an array for\nnow, to make ESQL more focused on one related integration.\n- New prompt to filter out one or more integrations from the returned\nRAG; similar to how its done for rules RAG results already.","sha":"0a7262d0fc213148fd7e80d3dc65f79c7eeae244"}},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Marius Iversen <marius.iversen@elastic.co> |
||
|---|---|---|
| .buildkite | ||
| .devcontainer | ||
| .github | ||
| api_docs | ||
| config | ||
| dev_docs | ||
| docs | ||
| examples | ||
| kbn_pm | ||
| legacy_rfcs | ||
| licenses | ||
| oas_docs | ||
| packages | ||
| plugins | ||
| scripts | ||
| src | ||
| test | ||
| typings | ||
| 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 | ||
| .puppeteerrc | ||
| .stylelintignore | ||
| .stylelintrc | ||
| .telemetryrc.json | ||
| .yarnrc | ||
| BUILD.bazel | ||
| catalog-info.yaml | ||
| CODE_OF_CONDUCT.md | ||
| CONTRIBUTING.md | ||
| FAQ.md | ||
| fleet_packages.json | ||
| github_checks_reporter.json | ||
| kibana.d.ts | ||
| LICENSE.txt | ||
| NOTICE.txt | ||
| package.json | ||
| preinstall_check.js | ||
| README.md | ||
| renovate.json | ||
| RISK_MATRIX.mdx | ||
| run_fleet_setup_parallel.sh | ||
| SECURITY.md | ||
| sonar-project.properties | ||
| STYLEGUIDE.mdx | ||
| tsconfig.base.json | ||
| tsconfig.browser.json | ||
| tsconfig.browser_bazel.json | ||
| tsconfig.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.