mirror of
https://github.com/elastic/kibana.git
synced 2025-04-24 17:59:23 -04:00
Your window into the Elastic Stack
8bdecd6641
# Backport This will backport the following commits from `main` to `8.x`: - [[ResponseOps][Rules] Ignore unknowns in the schema of the log threshold params (#217440)](https://github.com/elastic/kibana/pull/217440) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Christos Nasikas","email":"christos.nasikas@elastic.co"},"sourceCommit":{"committedDate":"2025-04-08T13:58:26Z","message":"[ResponseOps][Rules] Ignore unknowns in the schema of the log threshold params (#217440)\n\n## Summary\n\nA PR introduced into 8.18/9.0\n(https://github.com/elastic/kibana/pull/205507) changed the way we\nvalidate the log threshold rule type parameters. The validation happens\non rule params and changes a loose validation to a strict validation, so\nthose users who’ve inserted excess fields before 8.18/9.0 will see rules\nstarting to fail to run, their rule page failing to load and the API\nstarting to reject calls with excess fields.\n\nFixes: https://github.com/elastic/kibana/issues/217384\n\n## Testing instructions\n\n1. Start Kibana on 8.17 and create the following rule using the API. Let\nthe rule run.\n\n<details><summary>Rule</summary>\n\n```\n{\n \"name\": \"[QAF] Observability rule 3\",\n \"tags\": [\n \"metrics\",\n \"threshold\",\n \"qaf\"\n ],\n \"rule_type_id\": \"logs.alert.document.count\",\n \"consumer\": \"alerts\",\n \"schedule\": {\n \"interval\": \"1m\"\n },\n \"actions\": [],\n \"params\": {\n \"timeSize\": 8,\n \"timeUnit\": \"h\",\n \"count\": {\n \"value\": 1,\n \"comparator\": \"more than\"\n },\n \"criteria\": [\n {\n \"field\": \"bytes\",\n \"comparator\": \"more than\",\n \"value\": 1\n }\n ],\n \"logView\": {\n \"logViewId\": \"log-view-reference-0\",\n \"type\": \"log-view-reference\"\n },\n \"groupBy\": [\n \"geo.dest\"\n ],\n \"outputIndex\": \".alerts-observability.logs.alerts-default\"\n }\n}\n```\n\n</details> \n\n2. Start Kibana on 8.18. Verify that you cannot create the same rule and\nthe rule created in step 1 starts failing.\n3. Start Kibana on this PR and that you can create the same rule and the\nrule created in step 1 is working as expected.\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios","sha":"2a01722cfa42772b584e195eaebf4078e0cc5be2","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","Team:ResponseOps","v9.0.0","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[ResponseOps][Rules] Ignore unknowns in the schema of the log threshold params","number":217440,"url":"https://github.com/elastic/kibana/pull/217440","mergeCommit":{"message":"[ResponseOps][Rules] Ignore unknowns in the schema of the log threshold params (#217440)\n\n## Summary\n\nA PR introduced into 8.18/9.0\n(https://github.com/elastic/kibana/pull/205507) changed the way we\nvalidate the log threshold rule type parameters. The validation happens\non rule params and changes a loose validation to a strict validation, so\nthose users who’ve inserted excess fields before 8.18/9.0 will see rules\nstarting to fail to run, their rule page failing to load and the API\nstarting to reject calls with excess fields.\n\nFixes: https://github.com/elastic/kibana/issues/217384\n\n## Testing instructions\n\n1. Start Kibana on 8.17 and create the following rule using the API. Let\nthe rule run.\n\n<details><summary>Rule</summary>\n\n```\n{\n \"name\": \"[QAF] Observability rule 3\",\n \"tags\": [\n \"metrics\",\n \"threshold\",\n \"qaf\"\n ],\n \"rule_type_id\": \"logs.alert.document.count\",\n \"consumer\": \"alerts\",\n \"schedule\": {\n \"interval\": \"1m\"\n },\n \"actions\": [],\n \"params\": {\n \"timeSize\": 8,\n \"timeUnit\": \"h\",\n \"count\": {\n \"value\": 1,\n \"comparator\": \"more than\"\n },\n \"criteria\": [\n {\n \"field\": \"bytes\",\n \"comparator\": \"more than\",\n \"value\": 1\n }\n ],\n \"logView\": {\n \"logViewId\": \"log-view-reference-0\",\n \"type\": \"log-view-reference\"\n },\n \"groupBy\": [\n \"geo.dest\"\n ],\n \"outputIndex\": \".alerts-observability.logs.alerts-default\"\n }\n}\n```\n\n</details> \n\n2. Start Kibana on 8.18. Verify that you cannot create the same rule and\nthe rule created in step 1 starts failing.\n3. Start Kibana on this PR and that you can create the same rule and the\nrule created in step 1 is working as expected.\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios","sha":"2a01722cfa42772b584e195eaebf4078e0cc5be2"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.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/217440","number":217440,"mergeCommit":{"message":"[ResponseOps][Rules] Ignore unknowns in the schema of the log threshold params (#217440)\n\n## Summary\n\nA PR introduced into 8.18/9.0\n(https://github.com/elastic/kibana/pull/205507) changed the way we\nvalidate the log threshold rule type parameters. The validation happens\non rule params and changes a loose validation to a strict validation, so\nthose users who’ve inserted excess fields before 8.18/9.0 will see rules\nstarting to fail to run, their rule page failing to load and the API\nstarting to reject calls with excess fields.\n\nFixes: https://github.com/elastic/kibana/issues/217384\n\n## Testing instructions\n\n1. Start Kibana on 8.17 and create the following rule using the API. Let\nthe rule run.\n\n<details><summary>Rule</summary>\n\n```\n{\n \"name\": \"[QAF] Observability rule 3\",\n \"tags\": [\n \"metrics\",\n \"threshold\",\n \"qaf\"\n ],\n \"rule_type_id\": \"logs.alert.document.count\",\n \"consumer\": \"alerts\",\n \"schedule\": {\n \"interval\": \"1m\"\n },\n \"actions\": [],\n \"params\": {\n \"timeSize\": 8,\n \"timeUnit\": \"h\",\n \"count\": {\n \"value\": 1,\n \"comparator\": \"more than\"\n },\n \"criteria\": [\n {\n \"field\": \"bytes\",\n \"comparator\": \"more than\",\n \"value\": 1\n }\n ],\n \"logView\": {\n \"logViewId\": \"log-view-reference-0\",\n \"type\": \"log-view-reference\"\n },\n \"groupBy\": [\n \"geo.dest\"\n ],\n \"outputIndex\": \".alerts-observability.logs.alerts-default\"\n }\n}\n```\n\n</details> \n\n2. Start Kibana on 8.18. Verify that you cannot create the same rule and\nthe rule created in step 1 starts failing.\n3. Start Kibana on this PR and that you can create the same rule and the\nrule created in step 1 is working as expected.\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios","sha":"2a01722cfa42772b584e195eaebf4078e0cc5be2"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Christos Nasikas <christos.nasikas@elastic.co> |
||
|---|---|---|
| .buildkite | ||
| .devcontainer | ||
| .github | ||
| api_docs | ||
| config | ||
| dev_docs | ||
| docs | ||
| examples | ||
| kbn_pm | ||
| legacy_rfcs | ||
| licenses | ||
| oas_docs | ||
| packages | ||
| plugins | ||
| scripts | ||
| src | ||
| 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.