github-mirrors/kibana
1
0
Fork 0
mirror of https://github.com/elastic/kibana.git synced 2025-06-30 20:13:21 -04:00
Code Issues Projects Releases Packages Wiki Activity
83193 commits 499 branches 520 tags 21 GiB
Commit graph

83193 commits

This branch
This branch
All branches
Author SHA1 Message Date
kibanamachine
76d2227183 [CI] Auto-commit changed files from 'node scripts/build_plugin_list_docs' 2025-03-24 09:56:13 +00:00
Florent Le Borgne
261e6d8610
Add escaping to in-cell ES|QL pipe 2025-03-24 10:39:11 +01:00
Drew Tate
315e9b19ca
[8.x] [ES|QL] Remove command option definitions (#215425) (#215542) 
# Backport

This will backport the following commits from `main` to `8.x`:
- [[ES|QL] Remove command option definitions
(#215425)](https://github.com/elastic/kibana/pull/215425)

<!--- Backport version: 9.6.6 -->

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

<!--BACKPORT [{"author":{"name":"Drew
Tate","email":"drew.tate@elastic.co"},"sourceCommit":{"committedDate":"2025-03-21T11:04:33Z","message":"[ES|QL]
Remove command option definitions (#215425)\n\n## Summary\n\nThis PR
removes the declarative objects that were meant to describe
the\nbehavior of \"options\" (see details section below if you don't
know what\nI'm talking about). **It does not remove \"options\" as a
concept from our\nAST.** \"Option\" is probably the wrong name for the
subcommands in the\nAST but, at the moment, it is working fine how it
is.\n\nHere is a list of what these definitions were being used for and
where I\nended up.\n\n| Use | How it worked | What I did
|\n\n|---------------------------------------------------------------------|---------------|------------|\n|
To generate command declarations for display in suggestions menu |
It\nhad some complex logic to try to construct a declaration string from
the\ninformation in the `signature` property | I replaced this
with\nstatically declared declaration strings on the command
definitions. I\ntook most of them directly from our docs. They are a
better result than\nthe autogenerated stuff |\n| To build the `METADATA`
suggestion | the definition was passed into\n`buildOptionDefinition` | I
declared the `METADATA` suggestion\nstatically in the `FROM`
autocomplete code. |\n| To check for field correctness in `METADATA` |
This logic lived in the\noption definition's `validate` method | I moved
it to the `FROM`\ncommand's validate method |\n| To validate the type of
the value assigned to `APPEND_SEPARATOR` in\n`DISSECT` | This logic
lived in the option definition's `validate`\nmethod | I moved it to the
`DISSECT` command's validate method |\n| To check if the left side of
the equals sign in `DISSECT` is\n\"APPEND_SEPARATOR | In most cases, the
parser catches stuff like this,\nbut for some reason `DISSECT`'s grammar
is very loose so we have been\nstepping in with our own validation
(maybe we should suggest changing\nthis). This was the only case that
was triggering the \"Unknown option\"\nmessage. | I moved it to the
`DISSECT` command's validate method |\n| To prevent default column
validation for `METADATA` | This was the\nonly true use of the
`skipCommonValidation` property which would prevent\nthe validator
trying to find metadata fields in the standard field list\n| I inserted
an option name check directly into the validation code.\nIt's not a good
long-term solution, but it is actually an improvement\nsince the former
code pretended to be general but was actually just for\n`METADATA`. At
least now it is clear what the exception is for. |\n| To filter
functions and operators that are available after `BY` |\nFunction
definitions sometimes declare that they are supported in a
`by`\nstatement. The validator checks if the function does. | This
didn't\nchange. The option nodes in the AST are still there and we are
still\nrelying on the `supportedCommands` and `supportedOptions`
properties in\nthe function definitions. |\n\n#### Pictures\n\n<img
width=\"859\" alt=\"Screenshot 2025-03-20 at 1 47
36 PM\"\nsrc=\"https://github.com/user-attachments/assets/3bd3c3c6-6066-466e-b33b-9444ab58670a\"\n/>\n\n_New,
statically-defined declarations_\n\n<img width=\"783\" alt=\"Screenshot
2025-03-20 at 2 12
28 PM\"\nsrc=\"https://github.com/user-attachments/assets/94550b25-5da9-4c82-9586-11b3515debd7\"\n/>\n\n_In
cases besides `APPEND_SEPARATOR`, incorrect keywords produce
syntax\nerrors._\n\n<img width=\"700\" alt=\"Screenshot 2025-03-20 at 2
09
05 PM\"\nsrc=\"https://github.com/user-attachments/assets/de1a23f4-2509-4c6e-84ec-a807e96b65a5\"\n/>\n\n_Didn't
break the `APPEND_SEPARATOR` datatype validation_\n\n<img width=\"791\"
alt=\"Screenshot 2025-03-20 at 2 03
28 PM\"\nsrc=\"https://github.com/user-attachments/assets/169aaa15-52f3-4d22-ab77-26a560cd9359\"\n/>\n\n_Didn't
break `METADATA` fields validation_\n\n### Checklist\n\nCheck the PR
satisfies following conditions. \n\nReviewers should verify this PR
satisfies this list as well.\n\n- [x] Any text added follows [EUI's
writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\nsentence case text and includes
[i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n-
[x]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas
added for features that require explanation or tutorials\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\n\n###
Background/details\n\nTill now, \"options\" have been a concept in our
code. Their definition\nisn't clear, but it essentially comes down to
any capitalized keyword\nafter the command name. For example `STATS...
>BY<`, `DISSECT...\n>APPEND_SEPARATOR<`. You could think of them as
roughly subcommands or\nsubstatements.\n\nThere was a hope that commands
would be uniform enough that these\n\"options\" would deserve to be
their own special first-class citizen. But\nthey break
conceptually...\n\nFor example `APPEND_SEPARATOR` is not a keyword with
an expression after\nit... it is a variable `APPEND_SEPARATOR=\":\"`...
or filtering in\nstats.... `STATS AVG(bytes) >WHERE<` .... so is WHERE
an option now?\n\n`FORK` will break this even further.\n\nSo, we are
moving the architecture to allow for complexity and variance\namong the
commands. Command-specific logic will have the final say in\nhow
autocomplete and validation work for anything with that
command.","sha":"b7854a8759ca91255fe318c8d7a33b91996bf990","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Feature:ES|QL","Team:ESQL","backport:version","v9.1.0","v8.19.0"],"title":"[ES|QL]
Remove command option
definitions","number":215425,"url":"https://github.com/elastic/kibana/pull/215425","mergeCommit":{"message":"[ES|QL]
Remove command option definitions (#215425)\n\n## Summary\n\nThis PR
removes the declarative objects that were meant to describe
the\nbehavior of \"options\" (see details section below if you don't
know what\nI'm talking about). **It does not remove \"options\" as a
concept from our\nAST.** \"Option\" is probably the wrong name for the
subcommands in the\nAST but, at the moment, it is working fine how it
is.\n\nHere is a list of what these definitions were being used for and
where I\nended up.\n\n| Use | How it worked | What I did
|\n\n|---------------------------------------------------------------------|---------------|------------|\n|
To generate command declarations for display in suggestions menu |
It\nhad some complex logic to try to construct a declaration string from
the\ninformation in the `signature` property | I replaced this
with\nstatically declared declaration strings on the command
definitions. I\ntook most of them directly from our docs. They are a
better result than\nthe autogenerated stuff |\n| To build the `METADATA`
suggestion | the definition was passed into\n`buildOptionDefinition` | I
declared the `METADATA` suggestion\nstatically in the `FROM`
autocomplete code. |\n| To check for field correctness in `METADATA` |
This logic lived in the\noption definition's `validate` method | I moved
it to the `FROM`\ncommand's validate method |\n| To validate the type of
the value assigned to `APPEND_SEPARATOR` in\n`DISSECT` | This logic
lived in the option definition's `validate`\nmethod | I moved it to the
`DISSECT` command's validate method |\n| To check if the left side of
the equals sign in `DISSECT` is\n\"APPEND_SEPARATOR | In most cases, the
parser catches stuff like this,\nbut for some reason `DISSECT`'s grammar
is very loose so we have been\nstepping in with our own validation
(maybe we should suggest changing\nthis). This was the only case that
was triggering the \"Unknown option\"\nmessage. | I moved it to the
`DISSECT` command's validate method |\n| To prevent default column
validation for `METADATA` | This was the\nonly true use of the
`skipCommonValidation` property which would prevent\nthe validator
trying to find metadata fields in the standard field list\n| I inserted
an option name check directly into the validation code.\nIt's not a good
long-term solution, but it is actually an improvement\nsince the former
code pretended to be general but was actually just for\n`METADATA`. At
least now it is clear what the exception is for. |\n| To filter
functions and operators that are available after `BY` |\nFunction
definitions sometimes declare that they are supported in a
`by`\nstatement. The validator checks if the function does. | This
didn't\nchange. The option nodes in the AST are still there and we are
still\nrelying on the `supportedCommands` and `supportedOptions`
properties in\nthe function definitions. |\n\n#### Pictures\n\n<img
width=\"859\" alt=\"Screenshot 2025-03-20 at 1 47
36 PM\"\nsrc=\"https://github.com/user-attachments/assets/3bd3c3c6-6066-466e-b33b-9444ab58670a\"\n/>\n\n_New,
statically-defined declarations_\n\n<img width=\"783\" alt=\"Screenshot
2025-03-20 at 2 12
28 PM\"\nsrc=\"https://github.com/user-attachments/assets/94550b25-5da9-4c82-9586-11b3515debd7\"\n/>\n\n_In
cases besides `APPEND_SEPARATOR`, incorrect keywords produce
syntax\nerrors._\n\n<img width=\"700\" alt=\"Screenshot 2025-03-20 at 2
09
05 PM\"\nsrc=\"https://github.com/user-attachments/assets/de1a23f4-2509-4c6e-84ec-a807e96b65a5\"\n/>\n\n_Didn't
break the `APPEND_SEPARATOR` datatype validation_\n\n<img width=\"791\"
alt=\"Screenshot 2025-03-20 at 2 03
28 PM\"\nsrc=\"https://github.com/user-attachments/assets/169aaa15-52f3-4d22-ab77-26a560cd9359\"\n/>\n\n_Didn't
break `METADATA` fields validation_\n\n### Checklist\n\nCheck the PR
satisfies following conditions. \n\nReviewers should verify this PR
satisfies this list as well.\n\n- [x] Any text added follows [EUI's
writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\nsentence case text and includes
[i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n-
[x]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas
added for features that require explanation or tutorials\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\n\n###
Background/details\n\nTill now, \"options\" have been a concept in our
code. Their definition\nisn't clear, but it essentially comes down to
any capitalized keyword\nafter the command name. For example `STATS...
>BY<`, `DISSECT...\n>APPEND_SEPARATOR<`. You could think of them as
roughly subcommands or\nsubstatements.\n\nThere was a hope that commands
would be uniform enough that these\n\"options\" would deserve to be
their own special first-class citizen. But\nthey break
conceptually...\n\nFor example `APPEND_SEPARATOR` is not a keyword with
an expression after\nit... it is a variable `APPEND_SEPARATOR=\":\"`...
or filtering in\nstats.... `STATS AVG(bytes) >WHERE<` .... so is WHERE
an option now?\n\n`FORK` will break this even further.\n\nSo, we are
moving the architecture to allow for complexity and variance\namong the
commands. Command-specific logic will have the final say in\nhow
autocomplete and validation work for anything with that
command.","sha":"b7854a8759ca91255fe318c8d7a33b91996bf990"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/215425","number":215425,"mergeCommit":{"message":"[ES|QL]
Remove command option definitions (#215425)\n\n## Summary\n\nThis PR
removes the declarative objects that were meant to describe
the\nbehavior of \"options\" (see details section below if you don't
know what\nI'm talking about). **It does not remove \"options\" as a
concept from our\nAST.** \"Option\" is probably the wrong name for the
subcommands in the\nAST but, at the moment, it is working fine how it
is.\n\nHere is a list of what these definitions were being used for and
where I\nended up.\n\n| Use | How it worked | What I did
|\n\n|---------------------------------------------------------------------|---------------|------------|\n|
To generate command declarations for display in suggestions menu |
It\nhad some complex logic to try to construct a declaration string from
the\ninformation in the `signature` property | I replaced this
with\nstatically declared declaration strings on the command
definitions. I\ntook most of them directly from our docs. They are a
better result than\nthe autogenerated stuff |\n| To build the `METADATA`
suggestion | the definition was passed into\n`buildOptionDefinition` | I
declared the `METADATA` suggestion\nstatically in the `FROM`
autocomplete code. |\n| To check for field correctness in `METADATA` |
This logic lived in the\noption definition's `validate` method | I moved
it to the `FROM`\ncommand's validate method |\n| To validate the type of
the value assigned to `APPEND_SEPARATOR` in\n`DISSECT` | This logic
lived in the option definition's `validate`\nmethod | I moved it to the
`DISSECT` command's validate method |\n| To check if the left side of
the equals sign in `DISSECT` is\n\"APPEND_SEPARATOR | In most cases, the
parser catches stuff like this,\nbut for some reason `DISSECT`'s grammar
is very loose so we have been\nstepping in with our own validation
(maybe we should suggest changing\nthis). This was the only case that
was triggering the \"Unknown option\"\nmessage. | I moved it to the
`DISSECT` command's validate method |\n| To prevent default column
validation for `METADATA` | This was the\nonly true use of the
`skipCommonValidation` property which would prevent\nthe validator
trying to find metadata fields in the standard field list\n| I inserted
an option name check directly into the validation code.\nIt's not a good
long-term solution, but it is actually an improvement\nsince the former
code pretended to be general but was actually just for\n`METADATA`. At
least now it is clear what the exception is for. |\n| To filter
functions and operators that are available after `BY` |\nFunction
definitions sometimes declare that they are supported in a
`by`\nstatement. The validator checks if the function does. | This
didn't\nchange. The option nodes in the AST are still there and we are
still\nrelying on the `supportedCommands` and `supportedOptions`
properties in\nthe function definitions. |\n\n#### Pictures\n\n<img
width=\"859\" alt=\"Screenshot 2025-03-20 at 1 47
36 PM\"\nsrc=\"https://github.com/user-attachments/assets/3bd3c3c6-6066-466e-b33b-9444ab58670a\"\n/>\n\n_New,
statically-defined declarations_\n\n<img width=\"783\" alt=\"Screenshot
2025-03-20 at 2 12
28 PM\"\nsrc=\"https://github.com/user-attachments/assets/94550b25-5da9-4c82-9586-11b3515debd7\"\n/>\n\n_In
cases besides `APPEND_SEPARATOR`, incorrect keywords produce
syntax\nerrors._\n\n<img width=\"700\" alt=\"Screenshot 2025-03-20 at 2
09
05 PM\"\nsrc=\"https://github.com/user-attachments/assets/de1a23f4-2509-4c6e-84ec-a807e96b65a5\"\n/>\n\n_Didn't
break the `APPEND_SEPARATOR` datatype validation_\n\n<img width=\"791\"
alt=\"Screenshot 2025-03-20 at 2 03
28 PM\"\nsrc=\"https://github.com/user-attachments/assets/169aaa15-52f3-4d22-ab77-26a560cd9359\"\n/>\n\n_Didn't
break `METADATA` fields validation_\n\n### Checklist\n\nCheck the PR
satisfies following conditions. \n\nReviewers should verify this PR
satisfies this list as well.\n\n- [x] Any text added follows [EUI's
writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\nsentence case text and includes
[i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n-
[x]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas
added for features that require explanation or tutorials\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\n\n###
Background/details\n\nTill now, \"options\" have been a concept in our
code. Their definition\nisn't clear, but it essentially comes down to
any capitalized keyword\nafter the command name. For example `STATS...
>BY<`, `DISSECT...\n>APPEND_SEPARATOR<`. You could think of them as
roughly subcommands or\nsubstatements.\n\nThere was a hope that commands
would be uniform enough that these\n\"options\" would deserve to be
their own special first-class citizen. But\nthey break
conceptually...\n\nFor example `APPEND_SEPARATOR` is not a keyword with
an expression after\nit... it is a variable `APPEND_SEPARATOR=\":\"`...
or filtering in\nstats.... `STATS AVG(bytes) >WHERE<` .... so is WHERE
an option now?\n\n`FORK` will break this even further.\n\nSo, we are
moving the architecture to allow for complexity and variance\namong the
commands. Command-specific logic will have the final say in\nhow
autocomplete and validation work for anything with that
command.","sha":"b7854a8759ca91255fe318c8d7a33b91996bf990"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->
 2025-03-24 09:29:55 +01:00
Kibana Machine
95782f6d3a
[8.x] Register resident set size and limit bytes metrics in APM (#215458) (#215616) 
# Backport

This will backport the following commits from `main` to `8.x`:
- [Register resident set size and limit bytes metrics in APM
(#215458)](https://github.com/elastic/kibana/pull/215458)

<!--- Backport version: 9.6.6 -->

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

<!--BACKPORT [{"author":{"name":"Jesus
Wahrman","email":"41008968+jesuswr@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-23T21:22:30Z","message":"Register
resident set size and limit bytes metrics in APM (#215458)\n\n##
Summary\n\nResolves
https://github.com/elastic/kibana-team/issues/1565\n\nRegister resident
set size and limit bytes metrics in APM.\n\n<img width=\"1614\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/d5f1caf5-da4f-4acd-a63f-2b5256a91307\"\n/>\n\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\n- [x] The PR
description includes the appropriate Release Notes section,\nand the
correct `release_note:*` label is applied per
the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"04772fcc456aa6b03d9ecec540cc927c23c0dd9a","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Core","release_note:skip","backport:prev-major","backport:current-major","v9.1.0"],"title":"Register
resident set size and limit bytes metrics in
APM","number":215458,"url":"https://github.com/elastic/kibana/pull/215458","mergeCommit":{"message":"Register
resident set size and limit bytes metrics in APM (#215458)\n\n##
Summary\n\nResolves
https://github.com/elastic/kibana-team/issues/1565\n\nRegister resident
set size and limit bytes metrics in APM.\n\n<img width=\"1614\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/d5f1caf5-da4f-4acd-a63f-2b5256a91307\"\n/>\n\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\n- [x] The PR
description includes the appropriate Release Notes section,\nand the
correct `release_note:*` label is applied per
the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"04772fcc456aa6b03d9ecec540cc927c23c0dd9a"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/215458","number":215458,"mergeCommit":{"message":"Register
resident set size and limit bytes metrics in APM (#215458)\n\n##
Summary\n\nResolves
https://github.com/elastic/kibana-team/issues/1565\n\nRegister resident
set size and limit bytes metrics in APM.\n\n<img width=\"1614\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/d5f1caf5-da4f-4acd-a63f-2b5256a91307\"\n/>\n\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\n- [x] The PR
description includes the appropriate Release Notes section,\nand the
correct `release_note:*` label is applied per
the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"04772fcc456aa6b03d9ecec540cc927c23c0dd9a"}}]}]
BACKPORT-->

Co-authored-by: Jesus Wahrman <41008968+jesuswr@users.noreply.github.com>
 2025-03-24 01:16:05 +02:00
Gloria Hornero
4d53520eea
[8.x] initial @kbn/scout-security plugin (#210433) (#215527) 
# Backport

This will backport the following commits from `main` to `8.x`:
- [initial @kbn/scout-security plugin
(#210433)](https://github.com/elastic/kibana/pull/210433)

<!--- Backport version: 9.6.6 -->

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

<!--BACKPORT [{"author":{"name":"Gloria
Hornero","email":"gloria.hornero@elastic.co"},"sourceCommit":{"committedDate":"2025-03-21T10:59:30Z","message":"initial
@kbn/scout-security plugin (#210433)\n\n## Summary\n\nCloses
https://github.com/elastic/kibana/issues/210298\n\nIn this PR we are
adding the initial structure for the\n@kibana/scout-security package,
note that this is not ready to be used\nand any new test using this
package, is not going to be executed as part\nof the regular pipelines,
meaning, you are not going to add coverage to\nthe
application.
\n\n@kibana/scout-security package is a test package that
extends @kbn/scout\nwith test helpers specifically designed to test
Security Solution\nfunctionalities in Kibana. All tests under Security
plugins should only\nimport from @kbn/scout-security, not
from @kbn/scout.

\n\nThis PR is a POC to start testing development by
providing custom\nPlaywright fixtures, page objects, and utilities
tailored for\nSecurity-related testing scenarios.\n\nThings to
follow-up:

\n\n- CustomQueryRule interface is already declared
in\n`x-pack/solutions/security/plugins/security_solution/common/api/detection_engine/model/rule_schema/rule_schemas.gen.ts`\nas
`QueryRuleCreateProps`
\n- DETECTION_ENGINE_RULES_URL and
DETECTION_ENGINE_RULES_BULK_ACTION are\nalready declared in
`@kbn/security-solution-plugin/common/constants`\n\nIt would be great if
all of that is extracted from the plugin to a\npackage so it can be
reused instead of having to duplicate the code.\n\nUntil the package is
not ready to be used and has not been introduced to\nthe different
teams, appex-qa and myself will be the owners of it to\nmake sure that
best practices are followed\n\n---------\n\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by:
Dzmitry Lemechko
<dzmitry.lemechko@elastic.co>","sha":"d5a0501fb8148b4274a00921a6061d850b142f28","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:
SecuritySolution","backport:version","Team: Sec Eng
Productivity","test:scout","v9.1.0","v8.19.0"],"title":"initial
@kbn/scout-security
plugin","number":210433,"url":"https://github.com/elastic/kibana/pull/210433","mergeCommit":{"message":"initial
@kbn/scout-security plugin (#210433)\n\n## Summary\n\nCloses
https://github.com/elastic/kibana/issues/210298\n\nIn this PR we are
adding the initial structure for the\n@kibana/scout-security package,
note that this is not ready to be used\nand any new test using this
package, is not going to be executed as part\nof the regular pipelines,
meaning, you are not going to add coverage to\nthe
application.
\n\n@kibana/scout-security package is a test package that
extends @kbn/scout\nwith test helpers specifically designed to test
Security Solution\nfunctionalities in Kibana. All tests under Security
plugins should only\nimport from @kbn/scout-security, not
from @kbn/scout.

\n\nThis PR is a POC to start testing development by
providing custom\nPlaywright fixtures, page objects, and utilities
tailored for\nSecurity-related testing scenarios.\n\nThings to
follow-up:

\n\n- CustomQueryRule interface is already declared
in\n`x-pack/solutions/security/plugins/security_solution/common/api/detection_engine/model/rule_schema/rule_schemas.gen.ts`\nas
`QueryRuleCreateProps`
\n- DETECTION_ENGINE_RULES_URL and
DETECTION_ENGINE_RULES_BULK_ACTION are\nalready declared in
`@kbn/security-solution-plugin/common/constants`\n\nIt would be great if
all of that is extracted from the plugin to a\npackage so it can be
reused instead of having to duplicate the code.\n\nUntil the package is
not ready to be used and has not been introduced to\nthe different
teams, appex-qa and myself will be the owners of it to\nmake sure that
best practices are followed\n\n---------\n\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by:
Dzmitry Lemechko
<dzmitry.lemechko@elastic.co>","sha":"d5a0501fb8148b4274a00921a6061d850b142f28"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/210433","number":210433,"mergeCommit":{"message":"initial
@kbn/scout-security plugin (#210433)\n\n## Summary\n\nCloses
https://github.com/elastic/kibana/issues/210298\n\nIn this PR we are
adding the initial structure for the\n@kibana/scout-security package,
note that this is not ready to be used\nand any new test using this
package, is not going to be executed as part\nof the regular pipelines,
meaning, you are not going to add coverage to\nthe
application.
\n\n@kibana/scout-security package is a test package that
extends @kbn/scout\nwith test helpers specifically designed to test
Security Solution\nfunctionalities in Kibana. All tests under Security
plugins should only\nimport from @kbn/scout-security, not
from @kbn/scout.

\n\nThis PR is a POC to start testing development by
providing custom\nPlaywright fixtures, page objects, and utilities
tailored for\nSecurity-related testing scenarios.\n\nThings to
follow-up:

\n\n- CustomQueryRule interface is already declared
in\n`x-pack/solutions/security/plugins/security_solution/common/api/detection_engine/model/rule_schema/rule_schemas.gen.ts`\nas
`QueryRuleCreateProps`
\n- DETECTION_ENGINE_RULES_URL and
DETECTION_ENGINE_RULES_BULK_ACTION are\nalready declared in
`@kbn/security-solution-plugin/common/constants`\n\nIt would be great if
all of that is extracted from the plugin to a\npackage so it can be
reused instead of having to duplicate the code.\n\nUntil the package is
not ready to be used and has not been introduced to\nthe different
teams, appex-qa and myself will be the owners of it to\nmake sure that
best practices are followed\n\n---------\n\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by:
Dzmitry Lemechko
<dzmitry.lemechko@elastic.co>","sha":"d5a0501fb8148b4274a00921a6061d850b142f28"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
Co-authored-by: Dzmitry Lemechko <dzmitry.lemechko@elastic.co>
 2025-03-23 20:53:00 +02:00
Dzmitry Lemechko
b866dc9159
[8.x] [scout] extend config-discovery with CI validator (#214403) (#215343) 
# Backport

This will backport the following commits from `main` to `8.x`:
- [[scout] extend config-discovery with CI validator
(#214403)](https://github.com/elastic/kibana/pull/214403)

<!--- Backport version: 9.6.6 -->

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

<!--BACKPORT [{"author":{"name":"Dzmitry
Lemechko","email":"dzmitry.lemechko@elastic.co"},"sourceCommit":{"committedDate":"2025-03-18T20:24:54Z","message":"[scout]
extend config-discovery with CI validator (#214403)\n\n##
Summary\n\nMore teams are adding Scout tests in their plugins, often as
a PoC and\nnot stable yet for continuous execution.\nWe don't want to
block it, but need a way to manage the scope of Scout\npipeline and be
able to disable it quickly to unblock the Scout\ndevelopment.\n\nSince
Scout is in active development and we need it to be simple and\nquick as
possible (we can iterate and improve later), we agreed with\nRobert to
disable tests by plugin:\n\n```\nui_tests:\n enabled:\n - apm\n -
discover_enhanced\n - maps\n - observability_onboarding\n disabled:\n -
*skipped_plugin*\n```\n\nWhen scout configuration is added to the new
plugin, it will require to\nupdate `.buildkite/scout_ci_config.yml` that
is owned by `appex-qa`\nteam. If there is no intention to run Scout
tests on CI, plugin name\nshould be added under `disabled`
section.\n\n**How to test locally:**\n\n- Scout tests were added in
`observability_onboarding` plugin, pipeline\nwill throw error\n\nmodify
locally `.buildkite/scout_ci_config.yml`\n```\nui_tests:\n enabled:\n -
apm\n - discover_enhanced\n - maps\n disabled:\n```\n\nrun `node
scripts/scout discover-playwright-configs --validate
--save`\n\n```\nERROR The following plugins are not registered in Scout
CI config '.buildkite/scout_ci_config.yml'\n -
observability_onboarding\n```\n\n~~On CI annotation will be added to
clarify the failure:~~\n\nwe decided to move validation to \"Quick
Checks\", no need to annotate.\n\n<img width=\"1583\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/ed6b5778-74cb-4473-8218-b96239aab067\"\n/>\n\n\n-
`observability_onboarding` plugin is disabled, pipeline won't
include\nit (excluded in `scout_playwright_configs.json`)\n\nmodify
locally `.buildkite/scout_ci_config.yml`\n```\nui_tests:\n enabled:\n -
apm\n - discover_enhanced\n - maps\n disabled:\n -
observability_onboarding\n```\n\nrun `node scripts/scout
discover-playwright-configs --validate --save`\n\n```\n warn The
following plugins are disabled in '.buildkite/scout_ci_config.yml' and
will be excluded from CI run\n - observability_onboarding\n info Found
Playwright config files in '4' plugins.\n Saved '3' plugins to
'/Users/dmle/github/kibana/.scout/test_configs/scout_playwright_configs.json'\n```","sha":"05447fe978cd5fedbbaaf09e3f3d8ee41b760366","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:version","test:scout","v9.1.0","v8.19.0"],"title":"[scout]
extend config-discovery with CI
validator","number":214403,"url":"https://github.com/elastic/kibana/pull/214403","mergeCommit":{"message":"[scout]
extend config-discovery with CI validator (#214403)\n\n##
Summary\n\nMore teams are adding Scout tests in their plugins, often as
a PoC and\nnot stable yet for continuous execution.\nWe don't want to
block it, but need a way to manage the scope of Scout\npipeline and be
able to disable it quickly to unblock the Scout\ndevelopment.\n\nSince
Scout is in active development and we need it to be simple and\nquick as
possible (we can iterate and improve later), we agreed with\nRobert to
disable tests by plugin:\n\n```\nui_tests:\n enabled:\n - apm\n -
discover_enhanced\n - maps\n - observability_onboarding\n disabled:\n -
*skipped_plugin*\n```\n\nWhen scout configuration is added to the new
plugin, it will require to\nupdate `.buildkite/scout_ci_config.yml` that
is owned by `appex-qa`\nteam. If there is no intention to run Scout
tests on CI, plugin name\nshould be added under `disabled`
section.\n\n**How to test locally:**\n\n- Scout tests were added in
`observability_onboarding` plugin, pipeline\nwill throw error\n\nmodify
locally `.buildkite/scout_ci_config.yml`\n```\nui_tests:\n enabled:\n -
apm\n - discover_enhanced\n - maps\n disabled:\n```\n\nrun `node
scripts/scout discover-playwright-configs --validate
--save`\n\n```\nERROR The following plugins are not registered in Scout
CI config '.buildkite/scout_ci_config.yml'\n -
observability_onboarding\n```\n\n~~On CI annotation will be added to
clarify the failure:~~\n\nwe decided to move validation to \"Quick
Checks\", no need to annotate.\n\n<img width=\"1583\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/ed6b5778-74cb-4473-8218-b96239aab067\"\n/>\n\n\n-
`observability_onboarding` plugin is disabled, pipeline won't
include\nit (excluded in `scout_playwright_configs.json`)\n\nmodify
locally `.buildkite/scout_ci_config.yml`\n```\nui_tests:\n enabled:\n -
apm\n - discover_enhanced\n - maps\n disabled:\n -
observability_onboarding\n```\n\nrun `node scripts/scout
discover-playwright-configs --validate --save`\n\n```\n warn The
following plugins are disabled in '.buildkite/scout_ci_config.yml' and
will be excluded from CI run\n - observability_onboarding\n info Found
Playwright config files in '4' plugins.\n Saved '3' plugins to
'/Users/dmle/github/kibana/.scout/test_configs/scout_playwright_configs.json'\n```","sha":"05447fe978cd5fedbbaaf09e3f3d8ee41b760366"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/215340","number":215340,"state":"OPEN"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/214403","number":214403,"mergeCommit":{"message":"[scout]
extend config-discovery with CI validator (#214403)\n\n##
Summary\n\nMore teams are adding Scout tests in their plugins, often as
a PoC and\nnot stable yet for continuous execution.\nWe don't want to
block it, but need a way to manage the scope of Scout\npipeline and be
able to disable it quickly to unblock the Scout\ndevelopment.\n\nSince
Scout is in active development and we need it to be simple and\nquick as
possible (we can iterate and improve later), we agreed with\nRobert to
disable tests by plugin:\n\n```\nui_tests:\n enabled:\n - apm\n -
discover_enhanced\n - maps\n - observability_onboarding\n disabled:\n -
*skipped_plugin*\n```\n\nWhen scout configuration is added to the new
plugin, it will require to\nupdate `.buildkite/scout_ci_config.yml` that
is owned by `appex-qa`\nteam. If there is no intention to run Scout
tests on CI, plugin name\nshould be added under `disabled`
section.\n\n**How to test locally:**\n\n- Scout tests were added in
`observability_onboarding` plugin, pipeline\nwill throw error\n\nmodify
locally `.buildkite/scout_ci_config.yml`\n```\nui_tests:\n enabled:\n -
apm\n - discover_enhanced\n - maps\n disabled:\n```\n\nrun `node
scripts/scout discover-playwright-configs --validate
--save`\n\n```\nERROR The following plugins are not registered in Scout
CI config '.buildkite/scout_ci_config.yml'\n -
observability_onboarding\n```\n\n~~On CI annotation will be added to
clarify the failure:~~\n\nwe decided to move validation to \"Quick
Checks\", no need to annotate.\n\n<img width=\"1583\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/ed6b5778-74cb-4473-8218-b96239aab067\"\n/>\n\n\n-
`observability_onboarding` plugin is disabled, pipeline won't
include\nit (excluded in `scout_playwright_configs.json`)\n\nmodify
locally `.buildkite/scout_ci_config.yml`\n```\nui_tests:\n enabled:\n -
apm\n - discover_enhanced\n - maps\n disabled:\n -
observability_onboarding\n```\n\nrun `node scripts/scout
discover-playwright-configs --validate --save`\n\n```\n warn The
following plugins are disabled in '.buildkite/scout_ci_config.yml' and
will be excluded from CI run\n - observability_onboarding\n info Found
Playwright config files in '4' plugins.\n Saved '3' plugins to
'/Users/dmle/github/kibana/.scout/test_configs/scout_playwright_configs.json'\n```","sha":"05447fe978cd5fedbbaaf09e3f3d8ee41b760366"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
 2025-03-23 16:16:55 +01:00
Kibana Machine
55e7e9df31
[8.x] [ResponseOps] Adding back recovered alert optimization for the task state (#215344) (#215597) 
# Backport

This will backport the following commits from `main` to `8.x`:
- [[ResponseOps] Adding back recovered alert optimization for the task
state (#215344)](https://github.com/elastic/kibana/pull/215344)

<!--- Backport version: 9.6.6 -->

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

<!--BACKPORT [{"author":{"name":"Alexi
Doak","email":"109488926+doakalexi@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-22T00:21:16Z","message":"[ResponseOps]
Adding back recovered alert optimization for the task state
(#215344)\n\n## Summary\n\nI refactored the flapping code on ON week in
PR\nhttps://github.com/elastic/kibana/pull/213825 , and I removed
an\noptimization for removing recovered alerts from the task state that
we\ndon't need to track for flapping. This PR adds it back.\n\n\n###
Checklist\n\n- [ ] [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\n\n### To verify\n1.
Create an rule let it be active for a little and then let it
recover.\n2. Verify that once the flapping array doesn't have any `true`
values\nchanges","sha":"1dd1ec5870b342ee08b331ce3819461627f2d49a","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:ResponseOps","backport:version","v9.1.0","v8.19.0"],"title":"[ResponseOps]
Adding back recovered alert optimization for the task
state","number":215344,"url":"https://github.com/elastic/kibana/pull/215344","mergeCommit":{"message":"[ResponseOps]
Adding back recovered alert optimization for the task state
(#215344)\n\n## Summary\n\nI refactored the flapping code on ON week in
PR\nhttps://github.com/elastic/kibana/pull/213825 , and I removed
an\noptimization for removing recovered alerts from the task state that
we\ndon't need to track for flapping. This PR adds it back.\n\n\n###
Checklist\n\n- [ ] [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\n\n### To verify\n1.
Create an rule let it be active for a little and then let it
recover.\n2. Verify that once the flapping array doesn't have any `true`
values\nchanges","sha":"1dd1ec5870b342ee08b331ce3819461627f2d49a"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/215344","number":215344,"mergeCommit":{"message":"[ResponseOps]
Adding back recovered alert optimization for the task state
(#215344)\n\n## Summary\n\nI refactored the flapping code on ON week in
PR\nhttps://github.com/elastic/kibana/pull/213825 , and I removed
an\noptimization for removing recovered alerts from the task state that
we\ndon't need to track for flapping. This PR adds it back.\n\n\n###
Checklist\n\n- [ ] [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\n\n### To verify\n1.
Create an rule let it be active for a little and then let it
recover.\n2. Verify that once the flapping array doesn't have any `true`
values\nchanges","sha":"1dd1ec5870b342ee08b331ce3819461627f2d49a"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Alexi Doak <109488926+doakalexi@users.noreply.github.com>
 2025-03-22 04:11:46 +02:00
Kibana Machine
9c2c2519cd
[8.x] [Lens] fix drag and drop ghost after Chrome update to 134 (#213928) (#214126) 
# Backport

This will backport the following commits from `main` to `8.x`:
 - https://github.com/elastic/kibana/pull/213928
 - https://github.com/elastic/kibana/pull/215439

<!--- Backport version: 9.6.6 -->

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

<!--BACKPORT [{"author":{"name":"Marta
Bondyra","email":"4283304+mbondyra@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-12T11:30:51Z","message":"[Lens]
fix drag and drop ghost after Chrome update to 134 (#213928)\n\n##
Summary\nFixes https://github.com/elastic/kibana/issues/213708\n\nFixes
the ghost display. As @nickofthyme pointed
out\n[here](https://github.com/elastic/kibana/issues/213708#issuecomment-2712076212),\nthe
reason was using inset-inline-start: -10000px for the keyboard\nhandler
that is one of the children of the draggable component. The\nquick fix
is to just move it outside of the html element that is\ndragged.
@markov00 please assesswhere it should be merged
🙏🏼\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"84ae9c98c208957b3efc02c6b00bed8d567d4209","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Discover","release_note:fix","Team:Visualizations","Feature:Lens","backport:prev-minor","backport:prev-major","Feature:UnifiedFieldList","v9.1.0"],"title":"[Lens]
fix drag and drop ghost after Chrome update to
134","number":213928,"url":"https://github.com/elastic/kibana/pull/213928","mergeCommit":{"message":"[Lens]
fix drag and drop ghost after Chrome update to 134 (#213928)\n\n##
Summary\nFixes https://github.com/elastic/kibana/issues/213708\n\nFixes
the ghost display. As @nickofthyme pointed
out\n[here](https://github.com/elastic/kibana/issues/213708#issuecomment-2712076212),\nthe
reason was using inset-inline-start: -10000px for the keyboard\nhandler
that is one of the children of the draggable component. The\nquick fix
is to just move it outside of the html element that is\ndragged.
@markov00 please assesswhere it should be merged
🙏🏼\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"84ae9c98c208957b3efc02c6b00bed8d567d4209"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/213928","number":213928,"mergeCommit":{"message":"[Lens]
fix drag and drop ghost after Chrome update to 134 (#213928)\n\n##
Summary\nFixes https://github.com/elastic/kibana/issues/213708\n\nFixes
the ghost display. As @nickofthyme pointed
out\n[here](https://github.com/elastic/kibana/issues/213708#issuecomment-2712076212),\nthe
reason was using inset-inline-start: -10000px for the keyboard\nhandler
that is one of the children of the draggable component. The\nquick fix
is to just move it outside of the html element that is\ndragged.
@markov00 please assesswhere it should be merged
🙏🏼\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"84ae9c98c208957b3efc02c6b00bed8d567d4209"}}]}]
BACKPORT-->

---------

Co-authored-by: Marta Bondyra <4283304+mbondyra@users.noreply.github.com>
Co-authored-by: Nick Partridge <nicholas.partridge@elastic.co>
 2025-03-22 03:28:56 +02:00
Kibana Machine
7d32cf810e
[8.x] [Security Solution] [Attack discovery] Prompt updates (#215578) (#215589) 
# Backport

This will backport the following commits from `main` to `8.x`:
- [ [Security Solution] [Attack discovery] Prompt updates
(#215578)](https://github.com/elastic/kibana/pull/215578)

<!--- Backport version: 9.6.6 -->

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

<!--BACKPORT [{"author":{"name":"Andrew
Macri","email":"andrew.macri@elastic.co"},"sourceCommit":{"committedDate":"2025-03-21T23:06:37Z","message":"
[Security Solution] [Attack discovery] Prompt updates (#215578)\n\n##
[Security Solution] [Attack discovery] Prompt updates\n\nThis PR
contains updates to the following Attack discovery prompts:\n\n-
`attackDiscoveryPrompt`\n- `continuePrompt`\n- `refinePrompt`\n\nThank
you @mgarzon for these
improvements!","sha":"d52c5ed85cf31a14f3ee2b4c4d1ace62237fb23f","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:
SecuritySolution","Team:Security Generative
AI","backport:version","v8.18.0","v9.1.0","v8.19.0","v8.18.1","v9.0.1"],"title":"
[Security Solution] [Attack discovery] Prompt
updates","number":215578,"url":"https://github.com/elastic/kibana/pull/215578","mergeCommit":{"message":"
[Security Solution] [Attack discovery] Prompt updates (#215578)\n\n##
[Security Solution] [Attack discovery] Prompt updates\n\nThis PR
contains updates to the following Attack discovery prompts:\n\n-
`attackDiscoveryPrompt`\n- `continuePrompt`\n- `refinePrompt`\n\nThank
you @mgarzon for these
improvements!","sha":"d52c5ed85cf31a14f3ee2b4c4d1ace62237fb23f"}},"sourceBranch":"main","suggestedTargetBranches":["8.18","8.x","9.0"],"targetPullRequestStates":[{"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/215578","number":215578,"mergeCommit":{"message":"
[Security Solution] [Attack discovery] Prompt updates (#215578)\n\n##
[Security Solution] [Attack discovery] Prompt updates\n\nThis PR
contains updates to the following Attack discovery prompts:\n\n-
`attackDiscoveryPrompt`\n- `continuePrompt`\n- `refinePrompt`\n\nThank
you @mgarzon for these
improvements!","sha":"d52c5ed85cf31a14f3ee2b4c4d1ace62237fb23f"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Andrew Macri <andrew.macri@elastic.co>
 2025-03-22 03:00:19 +02:00
Kibana Machine
9f7c91d4a5
[8.x] [Dashboard] Composable content management transforms (#213831) (#215581) 
# Backport

This will backport the following commits from `main` to `8.x`:
- [[Dashboard] Composable content management transforms
(#213831)](https://github.com/elastic/kibana/pull/213831)

<!--- Backport version: 9.6.6 -->

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

<!--BACKPORT [{"author":{"name":"Nick
Peihl","email":"nick.peihl@elastic.co"},"sourceCommit":{"committedDate":"2025-03-21T22:04:39Z","message":"[Dashboard]
Composable content management transforms
(#213831)","sha":"f123b5096a92f980a4ea7d0b5410388c21c469e1","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Presentation","v9.0.0","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Dashboard]
Composable content management
transforms","number":213831,"url":"https://github.com/elastic/kibana/pull/213831","mergeCommit":{"message":"[Dashboard]
Composable content management transforms
(#213831)","sha":"f123b5096a92f980a4ea7d0b5410388c21c469e1"}},"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/213831","number":213831,"mergeCommit":{"message":"[Dashboard]
Composable content management transforms
(#213831)","sha":"f123b5096a92f980a4ea7d0b5410388c21c469e1"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Nick Peihl <nick.peihl@elastic.co>
 2025-03-22 01:48:17 +02:00
Kibana Machine
a664ea3d26
[8.x] Fixes Failing test: X-Pack Alerting API Integration Tests.x-pack/test/alerting_api_integration/security_and_spaces/group2/tests/telemetry/alerting_and_actions_telemetry·ts - alerting api integration security and spaces enabled - Group 2 Alerting and Actions Telemetry test telemetry should retrieve telemetry data in the expected format (#214868) (#215545) 
# Backport

This will backport the following commits from `main` to `8.x`:
- [Fixes Failing test: X-Pack Alerting API Integration
Tests.x-pack/test/alerting_api_integration/security_and_spaces/group2/tests/telemetry/alerting_and_actions_telemetry·ts
- alerting api integration security and spaces enabled - Group 2
Alerting and Actions Telemetry test telemetry should retrieve telemetry
data in the expected format
(#214868)](https://github.com/elastic/kibana/pull/214868)

<!--- Backport version: 9.6.6 -->

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

<!--BACKPORT [{"author":{"name":"Ying
Mao","email":"ying.mao@elastic.co"},"sourceCommit":{"committedDate":"2025-03-21T17:26:09Z","message":"Fixes
Failing test: X-Pack Alerting API Integration
Tests.x-pack/test/alerting_api_integration/security_and_spaces/group2/tests/telemetry/alerting_and_actions_telemetry·ts
- alerting api integration security and spaces enabled - Group 2
Alerting and Actions Telemetry test telemetry should retrieve telemetry
data in the expected format (#214868)\n\nResolves
https://github.com/elastic/kibana/issues/202564\n\n## Summary\n\nThe
test is testing for the number of alerts generated assuming the
AAD\nrule runs 3 times (2 alerts per run). It looks like sometimes, the
rule\nonly runs twice before the telemetry is collected so this updates
the\ntest to verify the number of alerts based on the number of times
the\nrule ran.\n\n---------\n\nCo-authored-by: Elastic Machine
<elasticmachine@users.noreply.github.com>","sha":"5e4981f18f171d8ebb2b0127d2cddf0324f618a4","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Alerting","release_note:skip","Team:ResponseOps","backport:version","v9.1.0","v8.19.0"],"title":"Fixes
Failing test: X-Pack Alerting API Integration
Tests.x-pack/test/alerting_api_integration/security_and_spaces/group2/tests/telemetry/alerting_and_actions_telemetry·ts
- alerting api integration security and spaces enabled - Group 2
Alerting and Actions Telemetry test telemetry should retrieve telemetry
data in the expected
format","number":214868,"url":"https://github.com/elastic/kibana/pull/214868","mergeCommit":{"message":"Fixes
Failing test: X-Pack Alerting API Integration
Tests.x-pack/test/alerting_api_integration/security_and_spaces/group2/tests/telemetry/alerting_and_actions_telemetry·ts
- alerting api integration security and spaces enabled - Group 2
Alerting and Actions Telemetry test telemetry should retrieve telemetry
data in the expected format (#214868)\n\nResolves
https://github.com/elastic/kibana/issues/202564\n\n## Summary\n\nThe
test is testing for the number of alerts generated assuming the
AAD\nrule runs 3 times (2 alerts per run). It looks like sometimes, the
rule\nonly runs twice before the telemetry is collected so this updates
the\ntest to verify the number of alerts based on the number of times
the\nrule ran.\n\n---------\n\nCo-authored-by: Elastic Machine
<elasticmachine@users.noreply.github.com>","sha":"5e4981f18f171d8ebb2b0127d2cddf0324f618a4"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/214868","number":214868,"mergeCommit":{"message":"Fixes
Failing test: X-Pack Alerting API Integration
Tests.x-pack/test/alerting_api_integration/security_and_spaces/group2/tests/telemetry/alerting_and_actions_telemetry·ts
- alerting api integration security and spaces enabled - Group 2
Alerting and Actions Telemetry test telemetry should retrieve telemetry
data in the expected format (#214868)\n\nResolves
https://github.com/elastic/kibana/issues/202564\n\n## Summary\n\nThe
test is testing for the number of alerts generated assuming the
AAD\nrule runs 3 times (2 alerts per run). It looks like sometimes, the
rule\nonly runs twice before the telemetry is collected so this updates
the\ntest to verify the number of alerts based on the number of times
the\nrule ran.\n\n---------\n\nCo-authored-by: Elastic Machine
<elasticmachine@users.noreply.github.com>","sha":"5e4981f18f171d8ebb2b0127d2cddf0324f618a4"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Ying Mao <ying.mao@elastic.co>
 2025-03-21 21:18:25 +02:00
Kibana Machine
a35581abae
[8.x] Unauthorized route migration for routes owned by kibana-management (#214782) (#215538) 
# Backport

This will backport the following commits from `main` to `8.x`:
- [Unauthorized route migration for routes owned by kibana-management
(#214782)](https://github.com/elastic/kibana/pull/214782)

<!--- Backport version: 9.6.6 -->

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

<!--BACKPORT [{"author":{"name":"Elena
Shostak","email":"165678770+elena-shostak@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-21T16:37:07Z","message":"Unauthorized
route migration for routes owned by kibana-management (#214782)\n\n###
Authz API migration for unauthorized routes\n\nThis PR migrates last
unauthorized routes owned by your team to a new\nsecurity
configuration.\nPlease refer to the documentation for more information:
[Authorization\nAPI](https://docs.elastic.dev/kibana-dev-docs/key-concepts/security-api-authorization)\n\n###
**Before migration:**\n```ts\nrouter.get({\n path: '/api/path',\n
...\n}, handler);\n```\n\n### **After
migration:**\n```ts\nrouter.get({\n path: '/api/path',\n security: {\n
authz: {\n enabled: false,\n reason: 'This route is opted out from
authorization because ...',\n },\n },\n ...\n},
handler);\n```","sha":"2160dd1d956a4d6dc6366dd0116ea68d58792537","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["enhancement","Team:Kibana
Management","release_note:skip","Feature:Security/Authorization","backport:prev-minor","backport:version","Authz:
API migration","v9.1.0","v8.19.0"],"title":"Unauthorized route migration
for routes owned by
kibana-management","number":214782,"url":"https://github.com/elastic/kibana/pull/214782","mergeCommit":{"message":"Unauthorized
route migration for routes owned by kibana-management (#214782)\n\n###
Authz API migration for unauthorized routes\n\nThis PR migrates last
unauthorized routes owned by your team to a new\nsecurity
configuration.\nPlease refer to the documentation for more information:
[Authorization\nAPI](https://docs.elastic.dev/kibana-dev-docs/key-concepts/security-api-authorization)\n\n###
**Before migration:**\n```ts\nrouter.get({\n path: '/api/path',\n
...\n}, handler);\n```\n\n### **After
migration:**\n```ts\nrouter.get({\n path: '/api/path',\n security: {\n
authz: {\n enabled: false,\n reason: 'This route is opted out from
authorization because ...',\n },\n },\n ...\n},
handler);\n```","sha":"2160dd1d956a4d6dc6366dd0116ea68d58792537"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/214782","number":214782,"mergeCommit":{"message":"Unauthorized
route migration for routes owned by kibana-management (#214782)\n\n###
Authz API migration for unauthorized routes\n\nThis PR migrates last
unauthorized routes owned by your team to a new\nsecurity
configuration.\nPlease refer to the documentation for more information:
[Authorization\nAPI](https://docs.elastic.dev/kibana-dev-docs/key-concepts/security-api-authorization)\n\n###
**Before migration:**\n```ts\nrouter.get({\n path: '/api/path',\n
...\n}, handler);\n```\n\n### **After
migration:**\n```ts\nrouter.get({\n path: '/api/path',\n security: {\n
authz: {\n enabled: false,\n reason: 'This route is opted out from
authorization because ...',\n },\n },\n ...\n},
handler);\n```","sha":"2160dd1d956a4d6dc6366dd0116ea68d58792537"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Elena Shostak <165678770+elena-shostak@users.noreply.github.com>
 2025-03-21 21:12:07 +02:00
wajihaparvez
3856985b1f
[Docs] 8.17.4 release notes (#215250) 
## Summary

Adding 8.17.4 release notes.

Rel: [3073](https://github.com/elastic/dev/issues/3073)
Closes: [659](https://github.com/elastic/platform-docs-team/issues/659)

<img width="802" alt="Screenshot 2025-03-19 at 5 26 25 PM"
src="https://github.com/user-attachments/assets/62726f13-44ce-4a61-b5c6-ab73956130d9"
/>
 2025-03-21 18:51:37 +00:00
wajihaparvez
85c84bd3d3
[Docs] 8.16.6 release notes (#215252) 
## Summary

Adding 8.16.6 release notes.

Rel: [3072](https://github.com/elastic/dev/issues/3072)
Closes: [658](https://github.com/elastic/platform-docs-team/issues/658)

<img width="872" alt="Screenshot 2025-03-19 at 5 29 05 PM"
src="https://github.com/user-attachments/assets/c06f7711-0c49-4be0-af19-86ac35d3f588"
/>
 2025-03-21 18:02:21 +00:00
Kibana Machine
9d825e0caa
[8.x] [EDR Workflows] Enable skipped defend workflows management cypress tests - response console processes (#215467) (#215523) 
# Backport

This will backport the following commits from `main` to `8.x`:
- [[EDR Workflows] Enable skipped defend workflows management cypress
tests - response console processes
(#215467)](https://github.com/elastic/kibana/pull/215467)

<!--- Backport version: 9.6.6 -->

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

<!--BACKPORT [{"author":{"name":"Gergő
Ábrahám","email":"gergo.abraham@elastic.co"},"sourceCommit":{"committedDate":"2025-03-21T15:06:09Z","message":"[EDR
Workflows] Enable skipped defend workflows management cypress tests -
response console processes (#215467)\n\n## Summary\n\nthis PR unskips
and fixes defend workflows cypress tests\n\nflaky
runner:\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8073\n-
50/50 ESS cypress ✅\n- serverless ✅ - lot of serverless tests failed
because of metering\ncypress test, but not because of processes
test\n\n> [!note]\n> flaky runner was performed together with metering
cypress test (see\nhttps://github.com/elastic/kibana/issues/187083),
which is indeed flaky,\nso it's removed from this PR\n\n\n- closes:
https://github.com/elastic/kibana/issues/170371\n- closes:
https://github.com/elastic/kibana/issues/170370\n- needs to be
backported to 8.18, 8.x, 9.0\n\n### Checklist\n\nCheck the PR satisfies
following conditions. \n\nReviewers should verify this PR satisfies this
list as well.\n\n- [x] [Flaky
Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)
was\nused on any tests
changed","sha":"a3f6c179b2da72cebc0be9920f3b85c4f9110a34","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Defend
Workflows","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[EDR
Workflows] Enable skipped defend workflows management cypress tests -
response console
processes","number":215467,"url":"https://github.com/elastic/kibana/pull/215467","mergeCommit":{"message":"[EDR
Workflows] Enable skipped defend workflows management cypress tests -
response console processes (#215467)\n\n## Summary\n\nthis PR unskips
and fixes defend workflows cypress tests\n\nflaky
runner:\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8073\n-
50/50 ESS cypress ✅\n- serverless ✅ - lot of serverless tests failed
because of metering\ncypress test, but not because of processes
test\n\n> [!note]\n> flaky runner was performed together with metering
cypress test (see\nhttps://github.com/elastic/kibana/issues/187083),
which is indeed flaky,\nso it's removed from this PR\n\n\n- closes:
https://github.com/elastic/kibana/issues/170371\n- closes:
https://github.com/elastic/kibana/issues/170370\n- needs to be
backported to 8.18, 8.x, 9.0\n\n### Checklist\n\nCheck the PR satisfies
following conditions. \n\nReviewers should verify this PR satisfies this
list as well.\n\n- [x] [Flaky
Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)
was\nused on any tests
changed","sha":"a3f6c179b2da72cebc0be9920f3b85c4f9110a34"}},"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/215467","number":215467,"mergeCommit":{"message":"[EDR
Workflows] Enable skipped defend workflows management cypress tests -
response console processes (#215467)\n\n## Summary\n\nthis PR unskips
and fixes defend workflows cypress tests\n\nflaky
runner:\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8073\n-
50/50 ESS cypress ✅\n- serverless ✅ - lot of serverless tests failed
because of metering\ncypress test, but not because of processes
test\n\n> [!note]\n> flaky runner was performed together with metering
cypress test (see\nhttps://github.com/elastic/kibana/issues/187083),
which is indeed flaky,\nso it's removed from this PR\n\n\n- closes:
https://github.com/elastic/kibana/issues/170371\n- closes:
https://github.com/elastic/kibana/issues/170370\n- needs to be
backported to 8.18, 8.x, 9.0\n\n### Checklist\n\nCheck the PR satisfies
following conditions. \n\nReviewers should verify this PR satisfies this
list as well.\n\n- [x] [Flaky
Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)
was\nused on any tests
changed","sha":"a3f6c179b2da72cebc0be9920f3b85c4f9110a34"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Gergő Ábrahám <gergo.abraham@elastic.co>
 2025-03-21 18:53:55 +02:00
Abhishek Bhatia
9135d4f4d2
[8.x] [Security Solution][Risk Score] Use Risk Engine SavedObject intead of localStorage on the Risk Score web page (#215304) (#215509) 
# Backport

This will backport the following commits from `main` to `8.x`:
- [[Security Solution][Risk Score] Use Risk Engine SavedObject intead of
localStorage on the Risk Score web page
(#215304)](https://github.com/elastic/kibana/pull/215304)

<!--- Backport version: 9.6.6 -->

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

<!--BACKPORT [{"author":{"name":"Abhishek
Bhatia","email":"117628830+abhishekbhatia1710@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-21T08:49:24Z","message":"[Security
Solution][Risk Score] Use Risk Engine SavedObject intead of localStorage
on the Risk Score web page (#215304)\n\n## Summary\n\nThe PR updates the
implementation to fetch data from the Risk Engine\nSaved Object instead
of storing and reusing it from LocalStorage.\n\nThis change ensures that
settings are applied globally rather than being\nlimited to the
browser’s LocalStorage. Since the Saved Object holds the\nmost
up-to-date information, it is now used to update the \"Date\" and
the\ntoggle for \"including closed alerts for risk scoring\" across all
web\nbrowsers.\n\n\n### Normal and Incognito Mode :
\n\n\n\nhttps://github.com/user-attachments/assets/7638c88b-ff9e-4d42-9944-e55b53e33518\n\n\n###
Default space vs custom space :
\n\n\n\nhttps://github.com/user-attachments/assets/46bb35c7-3cd9-4b97-9f1c-90ec4ef1241a\n\n\n##
Testing Steps\n\n### Verify Initial Values\n1. Open the Entity Risk
Score web page where the settings are applied.\n2. Ensure that the date
picker and toggle for \"including closed alerts\"\nreflect the values
stored in the Risk Engine Saved Object rather than\nLocalStorage.\n3.
Modify and Save changes,\n - Change the date range in the date picker.\n
- Toggle the \"Include Closed Alerts\" switch.\n\n### Page Refresh
Test\n- Refresh the page and confirm that the modified values persist,
fetched\ncorrectly from the Risk Engine Saved Object.\n\n###
Cross-Browser Test\n- Open the same web page in a different browser or
incognito mode.\n- Verify that the settings are consistent and correctly
loaded from the\nRisk Engine Saved\n Object.\n\n### Expected
Outcome\nThe settings should persist after a page refresh or across
different\nbrowsers.\nThe latest values should always be pulled from the
Risk Engine Saved\nObject.\n\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\n- [x] [Flaky
Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)
was\nused on any tests changed\n- [x] The PR description includes the
appropriate Release Notes section,\nand the correct `release_note:*`
label is applied per
the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"dbe28b9f94a16fa09684f65ae813eb178672d14e","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","v9.0.0","Team:Entity
Analytics","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Security
Solution][Risk Score] Use Risk Engine SavedObject intead of localStorage
on the Risk Score web
page","number":215304,"url":"https://github.com/elastic/kibana/pull/215304","mergeCommit":{"message":"[Security
Solution][Risk Score] Use Risk Engine SavedObject intead of localStorage
on the Risk Score web page (#215304)\n\n## Summary\n\nThe PR updates the
implementation to fetch data from the Risk Engine\nSaved Object instead
of storing and reusing it from LocalStorage.\n\nThis change ensures that
settings are applied globally rather than being\nlimited to the
browser’s LocalStorage. Since the Saved Object holds the\nmost
up-to-date information, it is now used to update the \"Date\" and
the\ntoggle for \"including closed alerts for risk scoring\" across all
web\nbrowsers.\n\n\n### Normal and Incognito Mode :
\n\n\n\nhttps://github.com/user-attachments/assets/7638c88b-ff9e-4d42-9944-e55b53e33518\n\n\n###
Default space vs custom space :
\n\n\n\nhttps://github.com/user-attachments/assets/46bb35c7-3cd9-4b97-9f1c-90ec4ef1241a\n\n\n##
Testing Steps\n\n### Verify Initial Values\n1. Open the Entity Risk
Score web page where the settings are applied.\n2. Ensure that the date
picker and toggle for \"including closed alerts\"\nreflect the values
stored in the Risk Engine Saved Object rather than\nLocalStorage.\n3.
Modify and Save changes,\n - Change the date range in the date picker.\n
- Toggle the \"Include Closed Alerts\" switch.\n\n### Page Refresh
Test\n- Refresh the page and confirm that the modified values persist,
fetched\ncorrectly from the Risk Engine Saved Object.\n\n###
Cross-Browser Test\n- Open the same web page in a different browser or
incognito mode.\n- Verify that the settings are consistent and correctly
loaded from the\nRisk Engine Saved\n Object.\n\n### Expected
Outcome\nThe settings should persist after a page refresh or across
different\nbrowsers.\nThe latest values should always be pulled from the
Risk Engine Saved\nObject.\n\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\n- [x] [Flaky
Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)
was\nused on any tests changed\n- [x] The PR description includes the
appropriate Release Notes section,\nand the correct `release_note:*`
label is applied per
the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"dbe28b9f94a16fa09684f65ae813eb178672d14e"}},"sourceBranch":"main","suggestedTargetBranches":["8.18","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/215440","number":215440,"state":"OPEN"},{"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/215304","number":215304,"mergeCommit":{"message":"[Security
Solution][Risk Score] Use Risk Engine SavedObject intead of localStorage
on the Risk Score web page (#215304)\n\n## Summary\n\nThe PR updates the
implementation to fetch data from the Risk Engine\nSaved Object instead
of storing and reusing it from LocalStorage.\n\nThis change ensures that
settings are applied globally rather than being\nlimited to the
browser’s LocalStorage. Since the Saved Object holds the\nmost
up-to-date information, it is now used to update the \"Date\" and
the\ntoggle for \"including closed alerts for risk scoring\" across all
web\nbrowsers.\n\n\n### Normal and Incognito Mode :
\n\n\n\nhttps://github.com/user-attachments/assets/7638c88b-ff9e-4d42-9944-e55b53e33518\n\n\n###
Default space vs custom space :
\n\n\n\nhttps://github.com/user-attachments/assets/46bb35c7-3cd9-4b97-9f1c-90ec4ef1241a\n\n\n##
Testing Steps\n\n### Verify Initial Values\n1. Open the Entity Risk
Score web page where the settings are applied.\n2. Ensure that the date
picker and toggle for \"including closed alerts\"\nreflect the values
stored in the Risk Engine Saved Object rather than\nLocalStorage.\n3.
Modify and Save changes,\n - Change the date range in the date picker.\n
- Toggle the \"Include Closed Alerts\" switch.\n\n### Page Refresh
Test\n- Refresh the page and confirm that the modified values persist,
fetched\ncorrectly from the Risk Engine Saved Object.\n\n###
Cross-Browser Test\n- Open the same web page in a different browser or
incognito mode.\n- Verify that the settings are consistent and correctly
loaded from the\nRisk Engine Saved\n Object.\n\n### Expected
Outcome\nThe settings should persist after a page refresh or across
different\nbrowsers.\nThe latest values should always be pulled from the
Risk Engine Saved\nObject.\n\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\n- [x] [Flaky
Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)
was\nused on any tests changed\n- [x] The PR description includes the
appropriate Release Notes section,\nand the correct `release_note:*`
label is applied per
the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"dbe28b9f94a16fa09684f65ae813eb178672d14e"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->
 2025-03-21 17:59:48 +02:00
Kibana Machine
a567ee2d7e
[8.x] [Search Profiler] Index field no longer resets on query edit (#215420) (#215499) 
# Backport

This will backport the following commits from `main` to `8.x`:
- [[Search Profiler] Index field no longer resets on query edit
(#215420)](https://github.com/elastic/kibana/pull/215420)

<!--- Backport version: 9.6.6 -->

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

<!--BACKPORT [{"author":{"name":"Matthew
Kime","email":"matt@mattki.me"},"sourceCommit":{"committedDate":"2025-03-21T13:29:33Z","message":"[Search
Profiler] Index field no longer resets on query edit (#215420)\n\n##
Summary\n\nPreviously, editing the query would reset the index field to
`_all`.\nThis was due to using `useState` instead of `useRef` to store
the query\nvalue.\n\nCloses
https://github.com/elastic/kibana/issues/214416\n\nHow to test\n1. Go to
search profiler\n2. Enter an index name, anything but `_all` - which is
already there\n3. Edit the query\n4. Did the index value remain
unchanged? Good! Its fixed!\n\nALSO - need to test to make sure this
works with content in the
url.","sha":"f77e29f5827c621d29959cbbf8514ce497565263","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Feature:Kibana
Management","Feature:Search
Profiler","backport:prev-major","v9.1.0"],"title":"[Search Profiler]
Index field no longer resets on query
edit","number":215420,"url":"https://github.com/elastic/kibana/pull/215420","mergeCommit":{"message":"[Search
Profiler] Index field no longer resets on query edit (#215420)\n\n##
Summary\n\nPreviously, editing the query would reset the index field to
`_all`.\nThis was due to using `useState` instead of `useRef` to store
the query\nvalue.\n\nCloses
https://github.com/elastic/kibana/issues/214416\n\nHow to test\n1. Go to
search profiler\n2. Enter an index name, anything but `_all` - which is
already there\n3. Edit the query\n4. Did the index value remain
unchanged? Good! Its fixed!\n\nALSO - need to test to make sure this
works with content in the
url.","sha":"f77e29f5827c621d29959cbbf8514ce497565263"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/215420","number":215420,"mergeCommit":{"message":"[Search
Profiler] Index field no longer resets on query edit (#215420)\n\n##
Summary\n\nPreviously, editing the query would reset the index field to
`_all`.\nThis was due to using `useState` instead of `useRef` to store
the query\nvalue.\n\nCloses
https://github.com/elastic/kibana/issues/214416\n\nHow to test\n1. Go to
search profiler\n2. Enter an index name, anything but `_all` - which is
already there\n3. Edit the query\n4. Did the index value remain
unchanged? Good! Its fixed!\n\nALSO - need to test to make sure this
works with content in the
url.","sha":"f77e29f5827c621d29959cbbf8514ce497565263"}}]}] BACKPORT-->

Co-authored-by: Matthew Kime <matt@mattki.me>
 2025-03-21 17:43:11 +02:00
Kibana Machine
4c9dccd842
[8.x] [Security Solution][Telemetry] Add ingest pipelines stats task (#213435) (#215501) 
# Backport

This will backport the following commits from `main` to `8.x`:
- [[Security Solution][Telemetry] Add ingest pipelines stats task
(#213435)](https://github.com/elastic/kibana/pull/213435)

<!--- Backport version: 9.6.6 -->

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

<!--BACKPORT [{"author":{"name":"Sebastián
Zaffarano","email":"sebastian.zaffarano@elastic.co"},"sourceCommit":{"committedDate":"2025-03-21T13:38:58Z","message":"[Security
Solution][Telemetry] Add ingest pipelines stats task (#213435)\n\n##
Summary\n\nAdd a new telemetry task to the security solution plugin to
collect\ningest pipeline stats. The new task runs once a day, calls
the\n`_nodes/stats/ingest` API, and sends an EBT event with the
following\ninformation:\n\n```js\nexport interface
NodeIngestPipelinesStats {\n name: string;\n totals: Totals;\n
pipelines: Pipeline[];\n}\n\nexport interface Pipeline {\n name:
string;\n totals: Totals;\n processors: Processor[];\n}\n\nexport
interface Processor {\n name: string;\n totals: Totals;\n}\n\nexport
interface Totals {\n count: number;\n time_in_millis: number;\n current:
number;\n failed: number;\n}\n```\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\n- [x] [Flaky
Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)
was\nused on any tests changed\n\n---------\n\nCo-authored-by: Elastic
Machine <elasticmachine@users.noreply.github.com>\nCo-authored-by:
Ryland Herrick
<ryalnd@gmail.com>","sha":"9cf3bea759591738cec5847454d789d33ff1d859","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:
SecuritySolution","backport:prev-minor","backport:prev-major","ci:build-cloud-image","ci:cloud-deploy","v9.1.0"],"title":"[Security
Solution][Telemetry] Add ingest pipelines stats
task","number":213435,"url":"https://github.com/elastic/kibana/pull/213435","mergeCommit":{"message":"[Security
Solution][Telemetry] Add ingest pipelines stats task (#213435)\n\n##
Summary\n\nAdd a new telemetry task to the security solution plugin to
collect\ningest pipeline stats. The new task runs once a day, calls
the\n`_nodes/stats/ingest` API, and sends an EBT event with the
following\ninformation:\n\n```js\nexport interface
NodeIngestPipelinesStats {\n name: string;\n totals: Totals;\n
pipelines: Pipeline[];\n}\n\nexport interface Pipeline {\n name:
string;\n totals: Totals;\n processors: Processor[];\n}\n\nexport
interface Processor {\n name: string;\n totals: Totals;\n}\n\nexport
interface Totals {\n count: number;\n time_in_millis: number;\n current:
number;\n failed: number;\n}\n```\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\n- [x] [Flaky
Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)
was\nused on any tests changed\n\n---------\n\nCo-authored-by: Elastic
Machine <elasticmachine@users.noreply.github.com>\nCo-authored-by:
Ryland Herrick
<ryalnd@gmail.com>","sha":"9cf3bea759591738cec5847454d789d33ff1d859"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/213435","number":213435,"mergeCommit":{"message":"[Security
Solution][Telemetry] Add ingest pipelines stats task (#213435)\n\n##
Summary\n\nAdd a new telemetry task to the security solution plugin to
collect\ningest pipeline stats. The new task runs once a day, calls
the\n`_nodes/stats/ingest` API, and sends an EBT event with the
following\ninformation:\n\n```js\nexport interface
NodeIngestPipelinesStats {\n name: string;\n totals: Totals;\n
pipelines: Pipeline[];\n}\n\nexport interface Pipeline {\n name:
string;\n totals: Totals;\n processors: Processor[];\n}\n\nexport
interface Processor {\n name: string;\n totals: Totals;\n}\n\nexport
interface Totals {\n count: number;\n time_in_millis: number;\n current:
number;\n failed: number;\n}\n```\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\n- [x] [Flaky
Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)
was\nused on any tests changed\n\n---------\n\nCo-authored-by: Elastic
Machine <elasticmachine@users.noreply.github.com>\nCo-authored-by:
Ryland Herrick
<ryalnd@gmail.com>","sha":"9cf3bea759591738cec5847454d789d33ff1d859"}}]}]
BACKPORT-->

Co-authored-by: Sebastián Zaffarano <sebastian.zaffarano@elastic.co>
 2025-03-21 17:39:16 +02:00
Kibana Machine
7b1eefddd1
[8.x] [ES|QL] Restructure validation code, remove command settings (#215056) (#215491) 
# Backport

This will backport the following commits from `main` to `8.x`:
- [[ES|QL] Restructure validation code, remove command settings
(#215056)](https://github.com/elastic/kibana/pull/215056)

<!--- Backport version: 9.6.6 -->

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

<!--BACKPORT [{"author":{"name":"Drew
Tate","email":"drew.tate@elastic.co"},"sourceCommit":{"committedDate":"2025-03-20T13:16:34Z","message":"[ES|QL]
Restructure validation code, remove command settings (#215056)\n\n##
Summary\n\nFollow on to several recent efforts
including\nhttps://github.com/elastic/kibana/issues/195418
and\nhttps://github.com/elastic/kibana/pull/213325\n\nThis PR\n-
reorganizes validation code to make dependencies clearer and make
it\nless overwhelming... it's not perfect but it's better\n- removes the
deprecated notion of a command \"setting\" which only ever\napplied to
`ENRICH`.\n\nNo regression in `ENRICH` mode validation:\n<img
width=\"874\" alt=\"Screenshot 2025-03-18 at 1 04
46 PM\"\nsrc=\"https://github.com/user-attachments/assets/e6639d8a-d129-440f-ac30-64a2ef6ab65c\"\n/>\n\nOr
hover\n<img width=\"419\" alt=\"Screenshot 2025-03-18 at 7 43
04 PM\"\nsrc=\"https://github.com/user-attachments/assets/8f9c020c-dcfd-42dc-8e14-4b1c4311457b\"\n/>\n\n\n\n\n\n###
Checklist\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\n\n---------\n\nCo-authored-by: Elastic Machine
<elasticmachine@users.noreply.github.com>","sha":"9073b194072cee0ef5290982c05cfdb84662c673","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["technical
debt","release_note:skip","Feature:ES|QL","Team:ESQL","backport:version","v9.1.0","v8.19.0"],"title":"[ES|QL]
Restructure validation code, remove command
settings","number":215056,"url":"https://github.com/elastic/kibana/pull/215056","mergeCommit":{"message":"[ES|QL]
Restructure validation code, remove command settings (#215056)\n\n##
Summary\n\nFollow on to several recent efforts
including\nhttps://github.com/elastic/kibana/issues/195418
and\nhttps://github.com/elastic/kibana/pull/213325\n\nThis PR\n-
reorganizes validation code to make dependencies clearer and make
it\nless overwhelming... it's not perfect but it's better\n- removes the
deprecated notion of a command \"setting\" which only ever\napplied to
`ENRICH`.\n\nNo regression in `ENRICH` mode validation:\n<img
width=\"874\" alt=\"Screenshot 2025-03-18 at 1 04
46 PM\"\nsrc=\"https://github.com/user-attachments/assets/e6639d8a-d129-440f-ac30-64a2ef6ab65c\"\n/>\n\nOr
hover\n<img width=\"419\" alt=\"Screenshot 2025-03-18 at 7 43
04 PM\"\nsrc=\"https://github.com/user-attachments/assets/8f9c020c-dcfd-42dc-8e14-4b1c4311457b\"\n/>\n\n\n\n\n\n###
Checklist\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\n\n---------\n\nCo-authored-by: Elastic Machine
<elasticmachine@users.noreply.github.com>","sha":"9073b194072cee0ef5290982c05cfdb84662c673"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/215056","number":215056,"mergeCommit":{"message":"[ES|QL]
Restructure validation code, remove command settings (#215056)\n\n##
Summary\n\nFollow on to several recent efforts
including\nhttps://github.com/elastic/kibana/issues/195418
and\nhttps://github.com/elastic/kibana/pull/213325\n\nThis PR\n-
reorganizes validation code to make dependencies clearer and make
it\nless overwhelming... it's not perfect but it's better\n- removes the
deprecated notion of a command \"setting\" which only ever\napplied to
`ENRICH`.\n\nNo regression in `ENRICH` mode validation:\n<img
width=\"874\" alt=\"Screenshot 2025-03-18 at 1 04
46 PM\"\nsrc=\"https://github.com/user-attachments/assets/e6639d8a-d129-440f-ac30-64a2ef6ab65c\"\n/>\n\nOr
hover\n<img width=\"419\" alt=\"Screenshot 2025-03-18 at 7 43
04 PM\"\nsrc=\"https://github.com/user-attachments/assets/8f9c020c-dcfd-42dc-8e14-4b1c4311457b\"\n/>\n\n\n\n\n\n###
Checklist\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\n\n---------\n\nCo-authored-by: Elastic Machine
<elasticmachine@users.noreply.github.com>","sha":"9073b194072cee0ef5290982c05cfdb84662c673"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Drew Tate <drew.tate@elastic.co>
 2025-03-21 17:17:46 +02:00
Konrad Szwarc
04433e758e
[8.x] [EDR Workflows] Unskip management Jest tests (#215324) (#215487) 
# Backport

This will backport the following commits from `main` to `8.x`:
- [[EDR Workflows] Unskip management Jest tests
(#215324)](https://github.com/elastic/kibana/pull/215324)

<!--- Backport version: 9.6.6 -->

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

<!--BACKPORT [{"author":{"name":"Konrad
Szwarc","email":"konrad.szwarc@elastic.co"},"sourceCommit":{"committedDate":"2025-03-21T12:26:30Z","message":"[EDR
Workflows] Unskip management Jest tests (#215324)\n\n8.17 PR -
https://github.com/elastic/kibana/pull/215474\nPart of
https://github.com/elastic/security-team/issues/12176\n\nUnskiped: \n###
`use_list_artifact.test.tsx`\nPath\n`.../plugins/security_solution/public/management/hooks/artifacts/use_list_artifact.test.tsx`\nCloses
https://github.com/elastic/kibana/issues/196724\nCommit
438553a1d167d97cc730405783e21963b6a790a7\nReason for unskipping:
Couldn't recreate failure locally. Increased\ntimeout from 1000 to 5000
ms.\n\n\n###
`actions_log_users_filter.test.tsx`\nPath\n`.../plugins/security_solution/public/management/components/endpoint_response_actions_list/components/actions_log_users_filter.test.tsx`\nCloses
https://github.com/elastic/kibana/issues/193554\nhttps://github.com/elastic/kibana/issues/193092\nCommit
ca7b97168318ca39eedb5afa6f67fe5e0ea304ed\nde03fd5448740e5d3b7059fedbd2cd511bec110f\nfb3910e738fab4e158852f60f4f5471732a5b191\nReason
for unskipping: wrapped expects in waitFor since they are\nawaiting for
state change. Increased the delay between keystrokes when\ntyping.
Increased the timeout of tests since locally they are bordering\n5s
executions.\n\n###
`bad_argument.test.tsx`\nPath\n`.../plugins/security_solution/public/management/components/console/components/bad_argument.test.tsx`\nCloses
https://github.com/elastic/kibana/issues/193093\nCommit
6959cd2e3fb53fb4c13d482456cf9ce76682f332\nReason for unskipping: wrapped
expects in waitFor since they are\nawaiting for state change. Increased
timeout to 10s.\n\n###
`use_get_endpoint_details.test.ts`\nPath\n`.../plugins/security_solution/public/management/hooks/endpoint/use_get_endpoint_details.test.ts`\nCloses
https://github.com/elastic/kibana/issues/192435\nCommit
3ba10029b62cc63db2c2565de2a2e9ec5b913539\nReason for unskipping:
increased timeout of waitFor for\nrenderReactQueryHook to 5s since
locally it was bordering 3
seconds","sha":"f09945bb1b5d4e00a953da8a8cd8d677f3d21ecc","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Defend
Workflows","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[EDR
Workflows] Unskip management Jest
tests","number":215324,"url":"https://github.com/elastic/kibana/pull/215324","mergeCommit":{"message":"[EDR
Workflows] Unskip management Jest tests (#215324)\n\n8.17 PR -
https://github.com/elastic/kibana/pull/215474\nPart of
https://github.com/elastic/security-team/issues/12176\n\nUnskiped: \n###
`use_list_artifact.test.tsx`\nPath\n`.../plugins/security_solution/public/management/hooks/artifacts/use_list_artifact.test.tsx`\nCloses
https://github.com/elastic/kibana/issues/196724\nCommit
438553a1d167d97cc730405783e21963b6a790a7\nReason for unskipping:
Couldn't recreate failure locally. Increased\ntimeout from 1000 to 5000
ms.\n\n\n###
`actions_log_users_filter.test.tsx`\nPath\n`.../plugins/security_solution/public/management/components/endpoint_response_actions_list/components/actions_log_users_filter.test.tsx`\nCloses
https://github.com/elastic/kibana/issues/193554\nhttps://github.com/elastic/kibana/issues/193092\nCommit
ca7b97168318ca39eedb5afa6f67fe5e0ea304ed\nde03fd5448740e5d3b7059fedbd2cd511bec110f\nfb3910e738fab4e158852f60f4f5471732a5b191\nReason
for unskipping: wrapped expects in waitFor since they are\nawaiting for
state change. Increased the delay between keystrokes when\ntyping.
Increased the timeout of tests since locally they are bordering\n5s
executions.\n\n###
`bad_argument.test.tsx`\nPath\n`.../plugins/security_solution/public/management/components/console/components/bad_argument.test.tsx`\nCloses
https://github.com/elastic/kibana/issues/193093\nCommit
6959cd2e3fb53fb4c13d482456cf9ce76682f332\nReason for unskipping: wrapped
expects in waitFor since they are\nawaiting for state change. Increased
timeout to 10s.\n\n###
`use_get_endpoint_details.test.ts`\nPath\n`.../plugins/security_solution/public/management/hooks/endpoint/use_get_endpoint_details.test.ts`\nCloses
https://github.com/elastic/kibana/issues/192435\nCommit
3ba10029b62cc63db2c2565de2a2e9ec5b913539\nReason for unskipping:
increased timeout of waitFor for\nrenderReactQueryHook to 5s since
locally it was bordering 3
seconds","sha":"f09945bb1b5d4e00a953da8a8cd8d677f3d21ecc"}},"sourceBranch":"main","suggestedTargetBranches":["8.18","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/215485","number":215485,"state":"OPEN"},{"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/215324","number":215324,"mergeCommit":{"message":"[EDR
Workflows] Unskip management Jest tests (#215324)\n\n8.17 PR -
https://github.com/elastic/kibana/pull/215474\nPart of
https://github.com/elastic/security-team/issues/12176\n\nUnskiped: \n###
`use_list_artifact.test.tsx`\nPath\n`.../plugins/security_solution/public/management/hooks/artifacts/use_list_artifact.test.tsx`\nCloses
https://github.com/elastic/kibana/issues/196724\nCommit
438553a1d167d97cc730405783e21963b6a790a7\nReason for unskipping:
Couldn't recreate failure locally. Increased\ntimeout from 1000 to 5000
ms.\n\n\n###
`actions_log_users_filter.test.tsx`\nPath\n`.../plugins/security_solution/public/management/components/endpoint_response_actions_list/components/actions_log_users_filter.test.tsx`\nCloses
https://github.com/elastic/kibana/issues/193554\nhttps://github.com/elastic/kibana/issues/193092\nCommit
ca7b97168318ca39eedb5afa6f67fe5e0ea304ed\nde03fd5448740e5d3b7059fedbd2cd511bec110f\nfb3910e738fab4e158852f60f4f5471732a5b191\nReason
for unskipping: wrapped expects in waitFor since they are\nawaiting for
state change. Increased the delay between keystrokes when\ntyping.
Increased the timeout of tests since locally they are bordering\n5s
executions.\n\n###
`bad_argument.test.tsx`\nPath\n`.../plugins/security_solution/public/management/components/console/components/bad_argument.test.tsx`\nCloses
https://github.com/elastic/kibana/issues/193093\nCommit
6959cd2e3fb53fb4c13d482456cf9ce76682f332\nReason for unskipping: wrapped
expects in waitFor since they are\nawaiting for state change. Increased
timeout to 10s.\n\n###
`use_get_endpoint_details.test.ts`\nPath\n`.../plugins/security_solution/public/management/hooks/endpoint/use_get_endpoint_details.test.ts`\nCloses
https://github.com/elastic/kibana/issues/192435\nCommit
3ba10029b62cc63db2c2565de2a2e9ec5b913539\nReason for unskipping:
increased timeout of waitFor for\nrenderReactQueryHook to 5s since
locally it was bordering 3
seconds","sha":"f09945bb1b5d4e00a953da8a8cd8d677f3d21ecc"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->
 2025-03-21 16:54:52 +02:00
Joe Reuter
8c9eccb437
[8.x] 🌊 Streams: Overview page redesign (#214196) (#215471) 
# Backport

This will backport the following commits from `main` to `8.x`:
- [🌊 Streams: Overview page redesign
(#214196)](https://github.com/elastic/kibana/pull/214196)

<!--- Backport version: 9.6.6 -->

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

<!--BACKPORT [{"author":{"name":"Joe
Reuter","email":"johannes.reuter@elastic.co"},"sourceCommit":{"committedDate":"2025-03-20T19:48:10Z","message":"🌊
Streams: Overview page redesign (#214196)\n\nThis PR overhauls the
overview page.\n\nClassic stream:\n<img width=\"1004\" alt=\"Screenshot
2025-03-12 at 21 00
39\"\nsrc=\"https://github.com/user-attachments/assets/a058da08-0ae2-48cc-abca-359b23288b32\"\n/>\n\nWired
stream:\n<img width=\"1019\" alt=\"Screenshot 2025-03-12 at 21 01
56\"\nsrc=\"https://github.com/user-attachments/assets/bca04537-f79b-4814-8e31-9d3dae18ad90\"\n/>\n\n\n##
Doubts / things I changed from the design\n\n* Quick links is just all
dashboards, so I adjusted the wording\naccordingly. Also, since we
render all dashboards, there isn't really\nvalue in \"View all
assets\"\n* The panel on top is already stating the count of docs, why
should we\nrepeat that in the histogram panel?\n* No search bar - in the
beginning we said we don't want this page to\nbecome discover, a search
bar feels like we are going there. Also, what\nshould the user enter
there? I don't think we want to buy deeper in KQL\n* Should the count of
docs be the total count of the count for the\ncurrently selected time
range? Not sure what makes more sense\n* For wired streams I left the
tabs in place to switch between child\nstreams and quick links. We can
revisit this once we get closer to\nactually releasing wired
streams\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"184d0a32adb2ec372c6427903d9269f813f04b6d","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:obs-ux-logs","backport:version","Feature:Streams","v9.1.0","v8.19.0"],"title":"🌊
Streams: Overview page
redesign","number":214196,"url":"https://github.com/elastic/kibana/pull/214196","mergeCommit":{"message":"🌊
Streams: Overview page redesign (#214196)\n\nThis PR overhauls the
overview page.\n\nClassic stream:\n<img width=\"1004\" alt=\"Screenshot
2025-03-12 at 21 00
39\"\nsrc=\"https://github.com/user-attachments/assets/a058da08-0ae2-48cc-abca-359b23288b32\"\n/>\n\nWired
stream:\n<img width=\"1019\" alt=\"Screenshot 2025-03-12 at 21 01
56\"\nsrc=\"https://github.com/user-attachments/assets/bca04537-f79b-4814-8e31-9d3dae18ad90\"\n/>\n\n\n##
Doubts / things I changed from the design\n\n* Quick links is just all
dashboards, so I adjusted the wording\naccordingly. Also, since we
render all dashboards, there isn't really\nvalue in \"View all
assets\"\n* The panel on top is already stating the count of docs, why
should we\nrepeat that in the histogram panel?\n* No search bar - in the
beginning we said we don't want this page to\nbecome discover, a search
bar feels like we are going there. Also, what\nshould the user enter
there? I don't think we want to buy deeper in KQL\n* Should the count of
docs be the total count of the count for the\ncurrently selected time
range? Not sure what makes more sense\n* For wired streams I left the
tabs in place to switch between child\nstreams and quick links. We can
revisit this once we get closer to\nactually releasing wired
streams\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"184d0a32adb2ec372c6427903d9269f813f04b6d"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/214196","number":214196,"mergeCommit":{"message":"🌊
Streams: Overview page redesign (#214196)\n\nThis PR overhauls the
overview page.\n\nClassic stream:\n<img width=\"1004\" alt=\"Screenshot
2025-03-12 at 21 00
39\"\nsrc=\"https://github.com/user-attachments/assets/a058da08-0ae2-48cc-abca-359b23288b32\"\n/>\n\nWired
stream:\n<img width=\"1019\" alt=\"Screenshot 2025-03-12 at 21 01
56\"\nsrc=\"https://github.com/user-attachments/assets/bca04537-f79b-4814-8e31-9d3dae18ad90\"\n/>\n\n\n##
Doubts / things I changed from the design\n\n* Quick links is just all
dashboards, so I adjusted the wording\naccordingly. Also, since we
render all dashboards, there isn't really\nvalue in \"View all
assets\"\n* The panel on top is already stating the count of docs, why
should we\nrepeat that in the histogram panel?\n* No search bar - in the
beginning we said we don't want this page to\nbecome discover, a search
bar feels like we are going there. Also, what\nshould the user enter
there? I don't think we want to buy deeper in KQL\n* Should the count of
docs be the total count of the count for the\ncurrently selected time
range? Not sure what makes more sense\n* For wired streams I left the
tabs in place to switch between child\nstreams and quick links. We can
revisit this once we get closer to\nactually releasing wired
streams\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"184d0a32adb2ec372c6427903d9269f813f04b6d"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
 2025-03-21 16:49:27 +02:00
Kibana Machine
79fee8aa38
[8.x] [ResponseOps][SecuritySolution][Alerts] Fix cases service missing in detection engine alerts table (#215111) (#215428) 
# Backport

This will backport the following commits from `main` to `8.x`:
- [[ResponseOps][SecuritySolution][Alerts] Fix cases service missing in
detection engine alerts table
(#215111)](https://github.com/elastic/kibana/pull/215111)

<!--- Backport version: 9.6.6 -->

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

<!--BACKPORT [{"author":{"name":"Umberto
Pepato","email":"umbopepato@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-20T22:57:30Z","message":"[ResponseOps][SecuritySolution][Alerts]
Fix cases service missing in detection engine alerts table
(#215111)\n\n## Summary\n\nProvides the Cases service to the detection
engine alerts table. The\nmissing services caused the cases actions to
disappear from the bulk\nactions menu.\n\n## Verification steps\n\n1.
Create Security rules that fire alerts\n2. Visit the Security > Alerts
page\n3. Select one or more alert rows from the table\n4. Open the
`Selected X alerts` bulk action menu\n5. Check that the cases bulk
actions are available\n\n## Release Notes\n\nFixes a regression that
caused the cases actions to disappear from the\ndetections engine alerts
table bulk actions menu.\n\n### Checklist\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\n- [x] The PR
description includes the appropriate Release Notes section,\nand the
correct `release_note:*` label is applied per
the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"7d6595768364d762764e8b891a97d85cdd0b259a","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:ResponseOps","backport:version","v9.1.0","v8.19.0"],"title":"[ResponseOps][SecuritySolution][Alerts]
Fix cases service missing in detection engine alerts
table","number":215111,"url":"https://github.com/elastic/kibana/pull/215111","mergeCommit":{"message":"[ResponseOps][SecuritySolution][Alerts]
Fix cases service missing in detection engine alerts table
(#215111)\n\n## Summary\n\nProvides the Cases service to the detection
engine alerts table. The\nmissing services caused the cases actions to
disappear from the bulk\nactions menu.\n\n## Verification steps\n\n1.
Create Security rules that fire alerts\n2. Visit the Security > Alerts
page\n3. Select one or more alert rows from the table\n4. Open the
`Selected X alerts` bulk action menu\n5. Check that the cases bulk
actions are available\n\n## Release Notes\n\nFixes a regression that
caused the cases actions to disappear from the\ndetections engine alerts
table bulk actions menu.\n\n### Checklist\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\n- [x] The PR
description includes the appropriate Release Notes section,\nand the
correct `release_note:*` label is applied per
the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"7d6595768364d762764e8b891a97d85cdd0b259a"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/215111","number":215111,"mergeCommit":{"message":"[ResponseOps][SecuritySolution][Alerts]
Fix cases service missing in detection engine alerts table
(#215111)\n\n## Summary\n\nProvides the Cases service to the detection
engine alerts table. The\nmissing services caused the cases actions to
disappear from the bulk\nactions menu.\n\n## Verification steps\n\n1.
Create Security rules that fire alerts\n2. Visit the Security > Alerts
page\n3. Select one or more alert rows from the table\n4. Open the
`Selected X alerts` bulk action menu\n5. Check that the cases bulk
actions are available\n\n## Release Notes\n\nFixes a regression that
caused the cases actions to disappear from the\ndetections engine alerts
table bulk actions menu.\n\n### Checklist\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\n- [x] The PR
description includes the appropriate Release Notes section,\nand the
correct `release_note:*` label is applied per
the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"7d6595768364d762764e8b891a97d85cdd0b259a"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Umberto Pepato <umbopepato@users.noreply.github.com>
 2025-03-21 16:32:43 +02:00
Kibana Machine
da948bc923
[8.x] Hide the chrome popup about leaked passwords (#215414) (#215480) 
# Backport

This will backport the following commits from `main` to `8.x`:
- [Hide the chrome popup about leaked passwords
(#215414)](https://github.com/elastic/kibana/pull/215414)

<!--- Backport version: 9.6.6 -->

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

<!--BACKPORT
[{"author":{"name":"Kurt","email":"kc13greiner@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-21T12:04:25Z","message":"Hide
the chrome popup about leaked passwords (#215414)\n\n## Summary\nCloses
https://github.com/elastic/kibana/issues/214355\n\nTesting with Chrome
135.x.x.x resulted in a pop up that was breaking the\nflow of
tests:\n\n<img width=\"470\" alt=\"Screenshot 2025-03-20 at 4 25
17 PM\"\nsrc=\"https://github.com/user-attachments/assets/df908294-1881-4b6d-b9a2-3027b37b06ad\"\n/>\n\nThis
isn't captured by the screenshotting plugin, but is visible if you\nrun
`headless=0`\n\nThis adds the config to disable that popup since our
generic testing\npasswords are very common and therefor
flagged","sha":"f5cebe2c23dff4454ec948358cc0a938400d5ede","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["chore","Team:Security","release_note:skip","backport:all-open","v9.1.0"],"title":"Hide
the chrome popup about leaked
passwords","number":215414,"url":"https://github.com/elastic/kibana/pull/215414","mergeCommit":{"message":"Hide
the chrome popup about leaked passwords (#215414)\n\n## Summary\nCloses
https://github.com/elastic/kibana/issues/214355\n\nTesting with Chrome
135.x.x.x resulted in a pop up that was breaking the\nflow of
tests:\n\n<img width=\"470\" alt=\"Screenshot 2025-03-20 at 4 25
17 PM\"\nsrc=\"https://github.com/user-attachments/assets/df908294-1881-4b6d-b9a2-3027b37b06ad\"\n/>\n\nThis
isn't captured by the screenshotting plugin, but is visible if you\nrun
`headless=0`\n\nThis adds the config to disable that popup since our
generic testing\npasswords are very common and therefor
flagged","sha":"f5cebe2c23dff4454ec948358cc0a938400d5ede"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/215414","number":215414,"mergeCommit":{"message":"Hide
the chrome popup about leaked passwords (#215414)\n\n## Summary\nCloses
https://github.com/elastic/kibana/issues/214355\n\nTesting with Chrome
135.x.x.x resulted in a pop up that was breaking the\nflow of
tests:\n\n<img width=\"470\" alt=\"Screenshot 2025-03-20 at 4 25
17 PM\"\nsrc=\"https://github.com/user-attachments/assets/df908294-1881-4b6d-b9a2-3027b37b06ad\"\n/>\n\nThis
isn't captured by the screenshotting plugin, but is visible if you\nrun
`headless=0`\n\nThis adds the config to disable that popup since our
generic testing\npasswords are very common and therefor
flagged","sha":"f5cebe2c23dff4454ec948358cc0a938400d5ede"}}]}]
BACKPORT-->

Co-authored-by: Kurt <kc13greiner@users.noreply.github.com>
 2025-03-21 15:58:10 +02:00
elastic-vault-github-plugin-prod[bot]
5a8914df6a
[8.x] Sync bundled packages with Package Storage (#215377) 
Automated by
https://buildkite.com/elastic/package-storage-infra-kibana-discover-release-branches/builds/2486

Co-authored-by: elasticmachine <elasticmachine@elastic.co>
Co-authored-by: Julia Bardi <90178898+juliaElastic@users.noreply.github.com>
 2025-03-21 15:28:38 +02:00
Kibana Machine
811a67d2e2
[8.x] [ResponseOps] Snooze Scheduler UX for recurring snoozes shows incorrect summary (#214797) (#215466) 
# Backport

This will backport the following commits from `main` to `8.x`:
- [[ResponseOps] Snooze Scheduler UX for recurring snoozes shows
incorrect summary
(#214797)](https://github.com/elastic/kibana/pull/214797)

<!--- Backport version: 9.6.6 -->

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

<!--BACKPORT
[{"author":{"name":"Julia","email":"iuliia.guskova@elastic.co"},"sourceCommit":{"committedDate":"2025-03-21T10:47:28Z","message":"[ResponseOps]
Snooze Scheduler UX for recurring snoozes shows incorrect summary
(#214797)\n\nSolves:
https://github.com/elastic/kibana/issues/210119\n\n## Summary\n\nHow to
test:\nReproduce bug from an issue. But create a rule in Stack
management.\nAction is not needed. You can test it on
main.\n![Screenshot 2025-03-19 at 20
43\n09](https://github.com/user-attachments/assets/2b311a28-c474-4883-8f75-34f9de87a493)\n\n![Screenshot
2025-03-19 at 20
46\n56](https://github.com/user-attachments/assets/894e26c6-b298-40c2-9d6a-c5fd460300d2)\n\nWhen
you add new schedule and save it, you should see proper date here\nas
well:\n\n![Screenshot 2025-03-19 at 20
59\n53](https://github.com/user-attachments/assets/28239de4-ee99-4e51-a88a-ca78e5248f5f)\n\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":"fdd872ada18ce7255cfac396a26dab46d9282dcb","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Alerting","release_note:skip","Team:ResponseOps","backport:version","v9.1.0","v8.19.0","v8.18.1","v8.16.6","v8.17.4"],"title":"[ResponseOps]
Snooze Scheduler UX for recurring snoozes shows incorrect summary
","number":214797,"url":"https://github.com/elastic/kibana/pull/214797","mergeCommit":{"message":"[ResponseOps]
Snooze Scheduler UX for recurring snoozes shows incorrect summary
(#214797)\n\nSolves:
https://github.com/elastic/kibana/issues/210119\n\n## Summary\n\nHow to
test:\nReproduce bug from an issue. But create a rule in Stack
management.\nAction is not needed. You can test it on
main.\n![Screenshot 2025-03-19 at 20
43\n09](https://github.com/user-attachments/assets/2b311a28-c474-4883-8f75-34f9de87a493)\n\n![Screenshot
2025-03-19 at 20
46\n56](https://github.com/user-attachments/assets/894e26c6-b298-40c2-9d6a-c5fd460300d2)\n\nWhen
you add new schedule and save it, you should see proper date here\nas
well:\n\n![Screenshot 2025-03-19 at 20
59\n53](https://github.com/user-attachments/assets/28239de4-ee99-4e51-a88a-ca78e5248f5f)\n\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":"fdd872ada18ce7255cfac396a26dab46d9282dcb"}},"sourceBranch":"main","suggestedTargetBranches":["8.x","8.18","8.16","8.17"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/214797","number":214797,"mergeCommit":{"message":"[ResponseOps]
Snooze Scheduler UX for recurring snoozes shows incorrect summary
(#214797)\n\nSolves:
https://github.com/elastic/kibana/issues/210119\n\n## Summary\n\nHow to
test:\nReproduce bug from an issue. But create a rule in Stack
management.\nAction is not needed. You can test it on
main.\n![Screenshot 2025-03-19 at 20
43\n09](https://github.com/user-attachments/assets/2b311a28-c474-4883-8f75-34f9de87a493)\n\n![Screenshot
2025-03-19 at 20
46\n56](https://github.com/user-attachments/assets/894e26c6-b298-40c2-9d6a-c5fd460300d2)\n\nWhen
you add new schedule and save it, you should see proper date here\nas
well:\n\n![Screenshot 2025-03-19 at 20
59\n53](https://github.com/user-attachments/assets/28239de4-ee99-4e51-a88a-ca78e5248f5f)\n\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":"fdd872ada18ce7255cfac396a26dab46d9282dcb"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.16","label":"v8.16.6","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.4","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Julia <iuliia.guskova@elastic.co>
 2025-03-21 14:39:56 +02:00
Kibana Machine
abf274a9df
[8.x] [Console] Fix auto-indentation issues (#214358) (#215460) 
# Backport

This will backport the following commits from `main` to `8.x`:
- [[Console] Fix auto-indentation issues
(#214358)](https://github.com/elastic/kibana/pull/214358)

<!--- Backport version: 9.6.6 -->

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

<!--BACKPORT [{"author":{"name":"Elena
Stoeva","email":"59341489+ElenaStoeva@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-21T10:23:43Z","message":"[Console]
Fix auto-indentation issues (#214358)\n\nFixes
https://github.com/elastic/kibana/issues/210231\nFixes
https://github.com/elastic/kibana/issues/212499\n\n## Summary\nTest
request:\n\n```\nGET _ingest/pipeline/_simulate\n{\n \"docs\": [\n {\n
\"_source\": {\n \"trace\": {\n \"name\": \"GET /actuator/health/**\"\n
},\n \"transaction\": {\n \"outcome\": \"success\"\n }\n }\n },\n {\n
\"_source\": {\n \"vulnerability\": {\n \"reference\": [\n
\"https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-15778\"\n ]\n
}\n }\n }\n
]\n}\n```","sha":"18aa055a6a65ebbe1957258c8044c420bd98c123","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Console","Team:Kibana
Management","release_note:skip","v9.0.0","backport:prev-minor","v9.1.0","v8.19.0"],"title":"[Console]
Fix auto-indentation
issues","number":214358,"url":"https://github.com/elastic/kibana/pull/214358","mergeCommit":{"message":"[Console]
Fix auto-indentation issues (#214358)\n\nFixes
https://github.com/elastic/kibana/issues/210231\nFixes
https://github.com/elastic/kibana/issues/212499\n\n## Summary\nTest
request:\n\n```\nGET _ingest/pipeline/_simulate\n{\n \"docs\": [\n {\n
\"_source\": {\n \"trace\": {\n \"name\": \"GET /actuator/health/**\"\n
},\n \"transaction\": {\n \"outcome\": \"success\"\n }\n }\n },\n {\n
\"_source\": {\n \"vulnerability\": {\n \"reference\": [\n
\"https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-15778\"\n ]\n
}\n }\n }\n
]\n}\n```","sha":"18aa055a6a65ebbe1957258c8044c420bd98c123"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.x"],"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/214358","number":214358,"mergeCommit":{"message":"[Console]
Fix auto-indentation issues (#214358)\n\nFixes
https://github.com/elastic/kibana/issues/210231\nFixes
https://github.com/elastic/kibana/issues/212499\n\n## Summary\nTest
request:\n\n```\nGET _ingest/pipeline/_simulate\n{\n \"docs\": [\n {\n
\"_source\": {\n \"trace\": {\n \"name\": \"GET /actuator/health/**\"\n
},\n \"transaction\": {\n \"outcome\": \"success\"\n }\n }\n },\n {\n
\"_source\": {\n \"vulnerability\": {\n \"reference\": [\n
\"https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-15778\"\n ]\n
}\n }\n }\n
]\n}\n```","sha":"18aa055a6a65ebbe1957258c8044c420bd98c123"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Elena Stoeva <59341489+ElenaStoeva@users.noreply.github.com>
 2025-03-21 14:28:12 +02:00
Kibana Machine
dcbf05e7d4
[8.x] Update dependency oniguruma-to-es to v4 (main) (#215073) (#215455) 
# Backport

This will backport the following commits from `main` to `8.x`:
- [Update dependency oniguruma-to-es to v4 (main)
(#215073)](https://github.com/elastic/kibana/pull/215073)

<!--- Backport version: 9.6.6 -->

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

<!--BACKPORT
[{"author":{"name":"elastic-renovate-prod[bot]","email":"174716857+elastic-renovate-prod[bot]@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-21T10:19:28Z","message":"Update
dependency oniguruma-to-es to v4 (main) (#215073)\n\nThis PR contains
the following updates:\n\n| Package | Type | Update | Change
|\n|---|---|---|---|\n|\n[oniguruma-to-es](https://redirect.github.com/slevithan/oniguruma-to-es)\n|
dependencies | major | [`^3.1.1`
->\n`^4.1.0`](https://renovatebot.com/diffs/npm/oniguruma-to-es/3.1.1/4.1.0)\n|\n\n---\n\n###
Release Notes\n\n<details>\n<summary>slevithan/oniguruma-to-es
(oniguruma-to-es)</summary>\n\n###\n[`v4.1.0`](https://redirect.github.com/slevithan/oniguruma-to-es/releases/tag/v4.1.0)\n\n[Compare\nSource](https://redirect.github.com/slevithan/oniguruma-to-es/compare/v4.0.1...v4.1.0)\n\n#####
🚀 Features\n\n- Added partial support for nested, negated classes with
`target`\n`ES2018` (supports top-level-nested, negated classes in
non-negated\nclasses).\n- Allows supporting output from
`oniguruma-parser/optimizer` in
older\nenvironments.\n\n###\n[`v4.0.1`](https://redirect.github.com/slevithan/oniguruma-to-es/releases/tag/v4.0.1)\n\n[Compare\nSource](https://redirect.github.com/slevithan/oniguruma-to-es/compare/v4.0.0...v4.0.1)\n\n#####
🐞 Fixes\n\n- Bumped the `oniguruma-parser` dependency to fix a bundle
size\nregression.\n\n###\n[`v4.0.0`](https://redirect.github.com/slevithan/oniguruma-to-es/releases/tag/v4.0.0)\n\n[Compare\nSource](https://redirect.github.com/slevithan/oniguruma-to-es/compare/v3.1.1...v4.0.0)\n\n#####
🚨 Breaking\n\n- Removed `toOnigurumaAst`. Its functionality has moved to
the new,\ndedicated
library\n[oniguruma-parser](https://redirect.github.com/slevithan/oniguruma-parser),\nwhich
includes many improvements, new features, and changes to the
AST\nstructure.\n\n##### 🚀 Features\n\n- `toRegExp`/`toRegExpDetails`:
Throw if the second argument isn't an\nobject or `undefined`.\n- Shorter
output for POSIX classes `cntrl`, `graph`, `print`.\n\n##### 🐞
Fixes\n\n- Fixed a regression in support for comment groups in
v3.1.1.\n([#&#8203;31](https://redirect.github.com/slevithan/oniguruma-to-es/issues/31))\n\n</details>\n\n---\n\n###
Configuration\n\n📅 **Schedule**: Branch creation - At any time (no
schedule defined),\nAutomerge - At any time (no schedule defined).\n\n🚦
**Automerge**: Disabled by config. Please merge this manually once
you\nare satisfied.\n\n♻ **Rebasing**: Whenever PR becomes conflicted,
or you tick the\nrebase/retry checkbox.\n\n🔕 **Ignore**: Close this PR
and you won't be reminded about this update\nagain.\n\n---\n\n- [ ] If
you want to rebase/retry this PR, check\nthis box\n\n---\n\nThis PR has
been generated by
[Renovate\nBot](https://redirect.github.com/renovatebot/renovate).\n\n\n\nCo-authored-by:
elastic-renovate-prod[bot]
<174716857+elastic-renovate-prod[bot]@users.noreply.github.com>\nCo-authored-by:
Kerry Gallagher
<kerry.gallagher@elastic.co>","sha":"0aa226cad4d0d15981788233950ffee76b235587","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:all-open","Team:obs-ux-logs","v9.1.0"],"title":"Update
dependency oniguruma-to-es to v4
(main)","number":215073,"url":"https://github.com/elastic/kibana/pull/215073","mergeCommit":{"message":"Update
dependency oniguruma-to-es to v4 (main) (#215073)\n\nThis PR contains
the following updates:\n\n| Package | Type | Update | Change
|\n|---|---|---|---|\n|\n[oniguruma-to-es](https://redirect.github.com/slevithan/oniguruma-to-es)\n|
dependencies | major | [`^3.1.1`
->\n`^4.1.0`](https://renovatebot.com/diffs/npm/oniguruma-to-es/3.1.1/4.1.0)\n|\n\n---\n\n###
Release Notes\n\n<details>\n<summary>slevithan/oniguruma-to-es
(oniguruma-to-es)</summary>\n\n###\n[`v4.1.0`](https://redirect.github.com/slevithan/oniguruma-to-es/releases/tag/v4.1.0)\n\n[Compare\nSource](https://redirect.github.com/slevithan/oniguruma-to-es/compare/v4.0.1...v4.1.0)\n\n#####
🚀 Features\n\n- Added partial support for nested, negated classes with
`target`\n`ES2018` (supports top-level-nested, negated classes in
non-negated\nclasses).\n- Allows supporting output from
`oniguruma-parser/optimizer` in
older\nenvironments.\n\n###\n[`v4.0.1`](https://redirect.github.com/slevithan/oniguruma-to-es/releases/tag/v4.0.1)\n\n[Compare\nSource](https://redirect.github.com/slevithan/oniguruma-to-es/compare/v4.0.0...v4.0.1)\n\n#####
🐞 Fixes\n\n- Bumped the `oniguruma-parser` dependency to fix a bundle
size\nregression.\n\n###\n[`v4.0.0`](https://redirect.github.com/slevithan/oniguruma-to-es/releases/tag/v4.0.0)\n\n[Compare\nSource](https://redirect.github.com/slevithan/oniguruma-to-es/compare/v3.1.1...v4.0.0)\n\n#####
🚨 Breaking\n\n- Removed `toOnigurumaAst`. Its functionality has moved to
the new,\ndedicated
library\n[oniguruma-parser](https://redirect.github.com/slevithan/oniguruma-parser),\nwhich
includes many improvements, new features, and changes to the
AST\nstructure.\n\n##### 🚀 Features\n\n- `toRegExp`/`toRegExpDetails`:
Throw if the second argument isn't an\nobject or `undefined`.\n- Shorter
output for POSIX classes `cntrl`, `graph`, `print`.\n\n##### 🐞
Fixes\n\n- Fixed a regression in support for comment groups in
v3.1.1.\n([#&#8203;31](https://redirect.github.com/slevithan/oniguruma-to-es/issues/31))\n\n</details>\n\n---\n\n###
Configuration\n\n📅 **Schedule**: Branch creation - At any time (no
schedule defined),\nAutomerge - At any time (no schedule defined).\n\n🚦
**Automerge**: Disabled by config. Please merge this manually once
you\nare satisfied.\n\n♻ **Rebasing**: Whenever PR becomes conflicted,
or you tick the\nrebase/retry checkbox.\n\n🔕 **Ignore**: Close this PR
and you won't be reminded about this update\nagain.\n\n---\n\n- [ ] If
you want to rebase/retry this PR, check\nthis box\n\n---\n\nThis PR has
been generated by
[Renovate\nBot](https://redirect.github.com/renovatebot/renovate).\n\n\n\nCo-authored-by:
elastic-renovate-prod[bot]
<174716857+elastic-renovate-prod[bot]@users.noreply.github.com>\nCo-authored-by:
Kerry Gallagher
<kerry.gallagher@elastic.co>","sha":"0aa226cad4d0d15981788233950ffee76b235587"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/215073","number":215073,"mergeCommit":{"message":"Update
dependency oniguruma-to-es to v4 (main) (#215073)\n\nThis PR contains
the following updates:\n\n| Package | Type | Update | Change
|\n|---|---|---|---|\n|\n[oniguruma-to-es](https://redirect.github.com/slevithan/oniguruma-to-es)\n|
dependencies | major | [`^3.1.1`
->\n`^4.1.0`](https://renovatebot.com/diffs/npm/oniguruma-to-es/3.1.1/4.1.0)\n|\n\n---\n\n###
Release Notes\n\n<details>\n<summary>slevithan/oniguruma-to-es
(oniguruma-to-es)</summary>\n\n###\n[`v4.1.0`](https://redirect.github.com/slevithan/oniguruma-to-es/releases/tag/v4.1.0)\n\n[Compare\nSource](https://redirect.github.com/slevithan/oniguruma-to-es/compare/v4.0.1...v4.1.0)\n\n#####
🚀 Features\n\n- Added partial support for nested, negated classes with
`target`\n`ES2018` (supports top-level-nested, negated classes in
non-negated\nclasses).\n- Allows supporting output from
`oniguruma-parser/optimizer` in
older\nenvironments.\n\n###\n[`v4.0.1`](https://redirect.github.com/slevithan/oniguruma-to-es/releases/tag/v4.0.1)\n\n[Compare\nSource](https://redirect.github.com/slevithan/oniguruma-to-es/compare/v4.0.0...v4.0.1)\n\n#####
🐞 Fixes\n\n- Bumped the `oniguruma-parser` dependency to fix a bundle
size\nregression.\n\n###\n[`v4.0.0`](https://redirect.github.com/slevithan/oniguruma-to-es/releases/tag/v4.0.0)\n\n[Compare\nSource](https://redirect.github.com/slevithan/oniguruma-to-es/compare/v3.1.1...v4.0.0)\n\n#####
🚨 Breaking\n\n- Removed `toOnigurumaAst`. Its functionality has moved to
the new,\ndedicated
library\n[oniguruma-parser](https://redirect.github.com/slevithan/oniguruma-parser),\nwhich
includes many improvements, new features, and changes to the
AST\nstructure.\n\n##### 🚀 Features\n\n- `toRegExp`/`toRegExpDetails`:
Throw if the second argument isn't an\nobject or `undefined`.\n- Shorter
output for POSIX classes `cntrl`, `graph`, `print`.\n\n##### 🐞
Fixes\n\n- Fixed a regression in support for comment groups in
v3.1.1.\n([#&#8203;31](https://redirect.github.com/slevithan/oniguruma-to-es/issues/31))\n\n</details>\n\n---\n\n###
Configuration\n\n📅 **Schedule**: Branch creation - At any time (no
schedule defined),\nAutomerge - At any time (no schedule defined).\n\n🚦
**Automerge**: Disabled by config. Please merge this manually once
you\nare satisfied.\n\n♻ **Rebasing**: Whenever PR becomes conflicted,
or you tick the\nrebase/retry checkbox.\n\n🔕 **Ignore**: Close this PR
and you won't be reminded about this update\nagain.\n\n---\n\n- [ ] If
you want to rebase/retry this PR, check\nthis box\n\n---\n\nThis PR has
been generated by
[Renovate\nBot](https://redirect.github.com/renovatebot/renovate).\n\n\n\nCo-authored-by:
elastic-renovate-prod[bot]
<174716857+elastic-renovate-prod[bot]@users.noreply.github.com>\nCo-authored-by:
Kerry Gallagher
<kerry.gallagher@elastic.co>","sha":"0aa226cad4d0d15981788233950ffee76b235587"}}]}]
BACKPORT-->

Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>
 2025-03-21 14:13:20 +02:00
Kibana Machine
22420c3535
[8.x] Unauthorized route migration for routes owned by search-kibana (#214786) (#215034) 
# Backport

This will backport the following commits from `main` to `8.x`:
- [Unauthorized route migration for routes owned by search-kibana
(#214786)](https://github.com/elastic/kibana/pull/214786)

<!--- Backport version: 9.6.6 -->

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

<!--BACKPORT [{"author":{"name":"Elena
Shostak","email":"165678770+elena-shostak@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-18T17:29:08Z","message":"Unauthorized
route migration for routes owned by search-kibana (#214786)\n\n### Authz
API migration for unauthorized routes\n\nThis PR migrates last
unauthorized routes owned by your team to a new\nsecurity
configuration.\nPlease refer to the documentation for more information:
[Authorization\nAPI](https://docs.elastic.dev/kibana-dev-docs/key-concepts/security-api-authorization)\n\n###
**Before migration:**\n```ts\nrouter.get({\n path: '/api/path',\n
...\n}, handler);\n```\n\n### **After
migration:**\n```ts\nrouter.get({\n path: '/api/path',\n security: {\n
authz: {\n enabled: false,\n reason: 'This route is opted out from
authorization because ...',\n },\n },\n ...\n},
handler);\n```","sha":"a3dd168cb1d8fb22a96e84994a6850b27a11d762","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["enhancement","release_note:skip","Feature:Security/Authorization","Team:Search","backport:prev-minor","backport:version","Authz:
API migration","v9.1.0","v8.19.0"],"title":"Unauthorized route migration
for routes owned by
search-kibana","number":214786,"url":"https://github.com/elastic/kibana/pull/214786","mergeCommit":{"message":"Unauthorized
route migration for routes owned by search-kibana (#214786)\n\n### Authz
API migration for unauthorized routes\n\nThis PR migrates last
unauthorized routes owned by your team to a new\nsecurity
configuration.\nPlease refer to the documentation for more information:
[Authorization\nAPI](https://docs.elastic.dev/kibana-dev-docs/key-concepts/security-api-authorization)\n\n###
**Before migration:**\n```ts\nrouter.get({\n path: '/api/path',\n
...\n}, handler);\n```\n\n### **After
migration:**\n```ts\nrouter.get({\n path: '/api/path',\n security: {\n
authz: {\n enabled: false,\n reason: 'This route is opted out from
authorization because ...',\n },\n },\n ...\n},
handler);\n```","sha":"a3dd168cb1d8fb22a96e84994a6850b27a11d762"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/214786","number":214786,"mergeCommit":{"message":"Unauthorized
route migration for routes owned by search-kibana (#214786)\n\n### Authz
API migration for unauthorized routes\n\nThis PR migrates last
unauthorized routes owned by your team to a new\nsecurity
configuration.\nPlease refer to the documentation for more information:
[Authorization\nAPI](https://docs.elastic.dev/kibana-dev-docs/key-concepts/security-api-authorization)\n\n###
**Before migration:**\n```ts\nrouter.get({\n path: '/api/path',\n
...\n}, handler);\n```\n\n### **After
migration:**\n```ts\nrouter.get({\n path: '/api/path',\n security: {\n
authz: {\n enabled: false,\n reason: 'This route is opted out from
authorization because ...',\n },\n },\n ...\n},
handler);\n```","sha":"a3dd168cb1d8fb22a96e84994a6850b27a11d762"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Elena Shostak <165678770+elena-shostak@users.noreply.github.com>
 2025-03-21 13:52:19 +02:00
Ignacio Rivas
fcf3a3ef45
[UA] Change default reindex flyout action based on index size (#215302) 2025-03-21 12:03:17 +01:00
florent-leborgne
cb36efc6a3
[Docs] ES|QL in Kibana updates (#215409) 
Includes:

- ES|QL dashboard controls
- Support for LOOKUP JOIN with autocomplete suggestions
- KQL/Lucene query carried over when switching to ES|QL mode
- ES|QL viz customization options

Rel: https://github.com/elastic/platform-docs-team/issues/614

Carried to 9.0+ docs with
https://github.com/elastic/docs-content/pull/857
 2025-03-21 10:41:27 +00:00
Kibana Machine
7a736864a9
[8.x] [APM] remove unnecessary field service.environment from top dependency spans endpoint (#215321) (#215360) 
# Backport

This will backport the following commits from `main` to `8.x`:
- [[APM] remove unnecessary field service.environment from top
dependency spans endpoint
(#215321)](https://github.com/elastic/kibana/pull/215321)

<!--- Backport version: 9.6.6 -->

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

<!--BACKPORT [{"author":{"name":"Sergi
Romeu","email":"sergi.romeu@elastic.co"},"sourceCommit":{"committedDate":"2025-03-20T15:31:36Z","message":"[APM]
remove unnecessary field service.environment from top dependency spans
endpoint (#215321)\n\n## Summary\n\nFixes #215106\n\nThis PR removes
`service.environment` as a required field for\n`getTopDependencySpans`
endpoint.\nIt was not used at all, so it can be safely removed without
adapting
the\nUI.","sha":"8193e56970757edc96fef17b18c6accbc1fad0dd","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","v9.0.0","apm","Team:obs-ux-infra_services","backport:version","v9.1.0","v8.19.0","v9.0.1"],"title":"[APM]
remove unnecessary field service.environment from top dependency spans
endpoint","number":215321,"url":"https://github.com/elastic/kibana/pull/215321","mergeCommit":{"message":"[APM]
remove unnecessary field service.environment from top dependency spans
endpoint (#215321)\n\n## Summary\n\nFixes #215106\n\nThis PR removes
`service.environment` as a required field for\n`getTopDependencySpans`
endpoint.\nIt was not used at all, so it can be safely removed without
adapting
the\nUI.","sha":"8193e56970757edc96fef17b18c6accbc1fad0dd"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.x"],"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/215321","number":215321,"mergeCommit":{"message":"[APM]
remove unnecessary field service.environment from top dependency spans
endpoint (#215321)\n\n## Summary\n\nFixes #215106\n\nThis PR removes
`service.environment` as a required field for\n`getTopDependencySpans`
endpoint.\nIt was not used at all, so it can be safely removed without
adapting
the\nUI.","sha":"8193e56970757edc96fef17b18c6accbc1fad0dd"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Sergi Romeu <sergi.romeu@elastic.co>
 2025-03-21 11:41:30 +02:00
Kibana Machine
d7d4bfd78f
[8.x] [ES|QL] Fixes the accessibility issue of the run button (#215277) (#215435) 
# Backport

This will backport the following commits from `main` to `8.x`:
- [[ES|QL] Fixes the accessibility issue of the run button
(#215277)](https://github.com/elastic/kibana/pull/215277)

<!--- Backport version: 9.6.6 -->

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

<!--BACKPORT [{"author":{"name":"Stratoula
Kalafateli","email":"efstratia.kalafateli@elastic.co"},"sourceCommit":{"committedDate":"2025-03-21T06:46:02Z","message":"[ES|QL]
Fixes the accessibility issue of the run button (#215277)\n\n##
Summary\n\nCloses
https://github.com/elastic/kibana/issues/214540\n\nSeparates the tooltip
label with the aria label for accessibility\nreasons\n\n<img
width=\"428\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/7aef7e8f-dc1d-4fce-ae05-cf6e215480af\"\n/>","sha":"6cd920c8e07b20d3d5060aa51694ec0ae9d7c197","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Feature:ES|QL","Team:ESQL","backport:version","v9.1.0","v8.19.0"],"title":"[ES|QL]
Fixes the accessibility issue of the run
button","number":215277,"url":"https://github.com/elastic/kibana/pull/215277","mergeCommit":{"message":"[ES|QL]
Fixes the accessibility issue of the run button (#215277)\n\n##
Summary\n\nCloses
https://github.com/elastic/kibana/issues/214540\n\nSeparates the tooltip
label with the aria label for accessibility\nreasons\n\n<img
width=\"428\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/7aef7e8f-dc1d-4fce-ae05-cf6e215480af\"\n/>","sha":"6cd920c8e07b20d3d5060aa51694ec0ae9d7c197"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/215277","number":215277,"mergeCommit":{"message":"[ES|QL]
Fixes the accessibility issue of the run button (#215277)\n\n##
Summary\n\nCloses
https://github.com/elastic/kibana/issues/214540\n\nSeparates the tooltip
label with the aria label for accessibility\nreasons\n\n<img
width=\"428\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/7aef7e8f-dc1d-4fce-ae05-cf6e215480af\"\n/>","sha":"6cd920c8e07b20d3d5060aa51694ec0ae9d7c197"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Stratoula Kalafateli <efstratia.kalafateli@elastic.co>
 2025-03-21 10:41:48 +02:00
Kibana Machine
c828ff8696
[8.x] [ES|QL] Calculate the query for retrieving the values correctly (#214905) (#215434) 
# Backport

This will backport the following commits from `main` to `8.x`:
- [[ES|QL] Calculate the query for retrieving the values correctly
(#214905)](https://github.com/elastic/kibana/pull/214905)

<!--- Backport version: 9.6.6 -->

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

<!--BACKPORT [{"author":{"name":"Stratoula
Kalafateli","email":"efstratia.kalafateli@elastic.co"},"sourceCommit":{"committedDate":"2025-03-21T06:44:39Z","message":"[ES|QL]
Calculate the query for retrieving the values correctly (#214905)\n\n##
Summary\n\nMy function to calculate the query for retrieving the values
wasn't\ncomplete. This fixes it by taking under consideration the
cursor\nposition\n\n\n![meow](https://github.com/user-attachments/assets/eac8bd8e-4e09-406e-969f-eb8dd95a0e61)\n\n\n###
Checklist\n- [ ] [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\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"96ba76de2b5cccbf71c7588e01d763bb45a6d7aa","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Feature:ES|QL","Team:ESQL","backport:version","v9.1.0","v8.19.0"],"title":"[ES|QL]
Calculate the query for retrieving the values
correctly","number":214905,"url":"https://github.com/elastic/kibana/pull/214905","mergeCommit":{"message":"[ES|QL]
Calculate the query for retrieving the values correctly (#214905)\n\n##
Summary\n\nMy function to calculate the query for retrieving the values
wasn't\ncomplete. This fixes it by taking under consideration the
cursor\nposition\n\n\n![meow](https://github.com/user-attachments/assets/eac8bd8e-4e09-406e-969f-eb8dd95a0e61)\n\n\n###
Checklist\n- [ ] [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\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"96ba76de2b5cccbf71c7588e01d763bb45a6d7aa"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/214905","number":214905,"mergeCommit":{"message":"[ES|QL]
Calculate the query for retrieving the values correctly (#214905)\n\n##
Summary\n\nMy function to calculate the query for retrieving the values
wasn't\ncomplete. This fixes it by taking under consideration the
cursor\nposition\n\n\n![meow](https://github.com/user-attachments/assets/eac8bd8e-4e09-406e-969f-eb8dd95a0e61)\n\n\n###
Checklist\n- [ ] [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\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"96ba76de2b5cccbf71c7588e01d763bb45a6d7aa"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Stratoula Kalafateli <efstratia.kalafateli@elastic.co>
 2025-03-21 10:38:20 +02:00
Kibana Machine
54388f7d78
[8.x] [Security Solution] Siem migration copy changes (#215220) (#215385) 
# Backport

This will backport the following commits from `main` to `8.x`:
- [[Security Solution] Siem migration copy changes
(#215220)](https://github.com/elastic/kibana/pull/215220)

<!--- Backport version: 9.6.6 -->

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

<!--BACKPORT [{"author":{"name":"Sergi
Massaneda","email":"sergi.massaneda@elastic.co"},"sourceCommit":{"committedDate":"2025-03-20T18:02:57Z","message":"[Security
Solution] Siem migration copy changes (#215220)\n\n##
Summary\n\nLast-minute copy changes\n\n<img width=\"788\"
alt=\"task\"\nsrc=\"https://github.com/user-attachments/assets/839b4d9c-67f6-43b9-a62e-4f1f974215ca\"\n/>","sha":"108716dce8d097a94b09e486c5876940c57158bd","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Threat
Hunting","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Security
Solution] Siem migration copy
changes","number":215220,"url":"https://github.com/elastic/kibana/pull/215220","mergeCommit":{"message":"[Security
Solution] Siem migration copy changes (#215220)\n\n##
Summary\n\nLast-minute copy changes\n\n<img width=\"788\"
alt=\"task\"\nsrc=\"https://github.com/user-attachments/assets/839b4d9c-67f6-43b9-a62e-4f1f974215ca\"\n/>","sha":"108716dce8d097a94b09e486c5876940c57158bd"}},"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/215220","number":215220,"mergeCommit":{"message":"[Security
Solution] Siem migration copy changes (#215220)\n\n##
Summary\n\nLast-minute copy changes\n\n<img width=\"788\"
alt=\"task\"\nsrc=\"https://github.com/user-attachments/assets/839b4d9c-67f6-43b9-a62e-4f1f974215ca\"\n/>","sha":"108716dce8d097a94b09e486c5876940c57158bd"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Sergi Massaneda <sergi.massaneda@elastic.co>
 2025-03-20 22:05:57 +02:00
Kibana Machine
106202fb10
[8.x] [ES|QL] AST/parser support for double param ?? (#215337) (#215372) 
# Backport

This will backport the following commits from `main` to `8.x`:
- [[ES|QL] AST/parser support for double param `??`
(#215337)](https://github.com/elastic/kibana/pull/215337)

<!--- Backport version: 9.6.6 -->

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

<!--BACKPORT [{"author":{"name":"Vadim
Kibana","email":"82822460+vadimkibana@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-20T16:43:50Z","message":"[ES|QL]
AST/parser support for double param `??` (#215337)\n\n## Summary\n\n-
Adds support for double param: (1) `??` unnamed; (2) `??name`
named;\nand (3) `??123` positional.\n- In the `@kbn/esql-ast`
package.\n- Adds types, parsing, builder and pretty-printing
support.\n\n\n### Checklist\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":"a94ff02ba00016f16f3ba271a81a177f60df3ae0","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["review","release_note:skip","Feature:ES|QL","Team:ESQL","backport:version","v9.1.0","v8.19.0"],"title":"[ES|QL]
AST/parser support for double param
`??`","number":215337,"url":"https://github.com/elastic/kibana/pull/215337","mergeCommit":{"message":"[ES|QL]
AST/parser support for double param `??` (#215337)\n\n## Summary\n\n-
Adds support for double param: (1) `??` unnamed; (2) `??name`
named;\nand (3) `??123` positional.\n- In the `@kbn/esql-ast`
package.\n- Adds types, parsing, builder and pretty-printing
support.\n\n\n### Checklist\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":"a94ff02ba00016f16f3ba271a81a177f60df3ae0"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/215337","number":215337,"mergeCommit":{"message":"[ES|QL]
AST/parser support for double param `??` (#215337)\n\n## Summary\n\n-
Adds support for double param: (1) `??` unnamed; (2) `??name`
named;\nand (3) `??123` positional.\n- In the `@kbn/esql-ast`
package.\n- Adds types, parsing, builder and pretty-printing
support.\n\n\n### Checklist\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":"a94ff02ba00016f16f3ba271a81a177f60df3ae0"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Vadim Kibana <82822460+vadimkibana@users.noreply.github.com>
 2025-03-20 20:36:22 +02:00
Kerry Gallagher
bbabd6d344
[8.x] [Streams 🌊] Enrichment - Add support for date processor (#213559) (#215359) 
# Backport

This will backport the following commits from `main` to `8.x`:
- [[Streams 🌊] Enrichment - Add support for date processor
(#213559)](https://github.com/elastic/kibana/pull/213559)

<!--- Backport version: 9.6.6 -->

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

<!--BACKPORT [{"author":{"name":"Marco Antonio
Ghiani","email":"marcoantonio.ghiani01@gmail.com"},"sourceCommit":{"committedDate":"2025-03-20T12:57:47Z","message":"[Streams
🌊] Enrichment - Add support for date processor (#213559)\n\n## 📓
Summary\n\nPart of
https://github.com/elastic/streams-program/issues/38\n\nThis work adds
the `date` processor along with the dissect and grok ones\nin the
enrichment section.\nIt scales well following the current folder
structure, but we should\ndefinitely polish it a bit more once more
processors get added, such as\ngetting the right form component, improve
form state derivation,
etc.\n\n\nhttps://github.com/user-attachments/assets/824d15c8-ce9d-455a-ae0b-97aeec8cf025\n\n---------\n\nCo-authored-by:
Kerry Gallagher <kerry.gallagher@elastic.co>\nCo-authored-by: Joe Reuter
<johannes.reuter@elastic.co>\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Kerry
Gallagher
<471693+Kerry350@users.noreply.github.com>","sha":"8f65dceefca69c70de33be8176942d0c89fb0e27","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:obs-ux-logs","backport:version","Feature:Streams","v9.1.0","v8.19.0"],"title":"[Streams
🌊] Enrichment - Add support for date
processor","number":213559,"url":"https://github.com/elastic/kibana/pull/213559","mergeCommit":{"message":"[Streams
🌊] Enrichment - Add support for date processor (#213559)\n\n## 📓
Summary\n\nPart of
https://github.com/elastic/streams-program/issues/38\n\nThis work adds
the `date` processor along with the dissect and grok ones\nin the
enrichment section.\nIt scales well following the current folder
structure, but we should\ndefinitely polish it a bit more once more
processors get added, such as\ngetting the right form component, improve
form state derivation,
etc.\n\n\nhttps://github.com/user-attachments/assets/824d15c8-ce9d-455a-ae0b-97aeec8cf025\n\n---------\n\nCo-authored-by:
Kerry Gallagher <kerry.gallagher@elastic.co>\nCo-authored-by: Joe Reuter
<johannes.reuter@elastic.co>\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Kerry
Gallagher
<471693+Kerry350@users.noreply.github.com>","sha":"8f65dceefca69c70de33be8176942d0c89fb0e27"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/213559","number":213559,"mergeCommit":{"message":"[Streams
🌊] Enrichment - Add support for date processor (#213559)\n\n## 📓
Summary\n\nPart of
https://github.com/elastic/streams-program/issues/38\n\nThis work adds
the `date` processor along with the dissect and grok ones\nin the
enrichment section.\nIt scales well following the current folder
structure, but we should\ndefinitely polish it a bit more once more
processors get added, such as\ngetting the right form component, improve
form state derivation,
etc.\n\n\nhttps://github.com/user-attachments/assets/824d15c8-ce9d-455a-ae0b-97aeec8cf025\n\n---------\n\nCo-authored-by:
Kerry Gallagher <kerry.gallagher@elastic.co>\nCo-authored-by: Joe Reuter
<johannes.reuter@elastic.co>\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Kerry
Gallagher
<471693+Kerry350@users.noreply.github.com>","sha":"8f65dceefca69c70de33be8176942d0c89fb0e27"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

---------

Co-authored-by: Marco Antonio Ghiani <marcoantonio.ghiani01@gmail.com>
Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
 2025-03-20 20:24:06 +02:00
Kibana Machine
0a7f9f74dc
[8.x] [ES|QL] Match expression support in the ES|QL AST package (#215336) (#215367) 
# Backport

This will backport the following commits from `main` to `8.x`:
- [[ES|QL] Match expression support in the ES|QL AST package
(#215336)](https://github.com/elastic/kibana/pull/215336)

<!--- Backport version: 9.6.6 -->

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

<!--BACKPORT [{"author":{"name":"Vadim
Kibana","email":"82822460+vadimkibana@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-20T16:19:45Z","message":"[ES|QL]
Match expression support in the ES|QL AST package (#215336)\n\n##
Summary\n\nPartially addresses
https://github.com/elastic/kibana/issues/214359\n\n- Adds support for
*MatchExpression* in `WHERE` command.\n - `WHERE column :: cast :
condition`\n - Support for cast and condition parsing\n - Support for
pretty-printing\n\n\n\n### Checklist\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":"c8abafc6e7a63beeed404b0ea1d2a4dfd7777dc2","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["review","release_note:skip","Feature:ES|QL","Team:ESQL","backport:version","v9.1.0","v8.19.0"],"title":"[ES|QL]
Match expression support in the ES|QL AST
package","number":215336,"url":"https://github.com/elastic/kibana/pull/215336","mergeCommit":{"message":"[ES|QL]
Match expression support in the ES|QL AST package (#215336)\n\n##
Summary\n\nPartially addresses
https://github.com/elastic/kibana/issues/214359\n\n- Adds support for
*MatchExpression* in `WHERE` command.\n - `WHERE column :: cast :
condition`\n - Support for cast and condition parsing\n - Support for
pretty-printing\n\n\n\n### Checklist\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":"c8abafc6e7a63beeed404b0ea1d2a4dfd7777dc2"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/215336","number":215336,"mergeCommit":{"message":"[ES|QL]
Match expression support in the ES|QL AST package (#215336)\n\n##
Summary\n\nPartially addresses
https://github.com/elastic/kibana/issues/214359\n\n- Adds support for
*MatchExpression* in `WHERE` command.\n - `WHERE column :: cast :
condition`\n - Support for cast and condition parsing\n - Support for
pretty-printing\n\n\n\n### Checklist\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":"c8abafc6e7a63beeed404b0ea1d2a4dfd7777dc2"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Vadim Kibana <82822460+vadimkibana@users.noreply.github.com>
 2025-03-20 20:23:46 +02:00
Kibana Machine
915a7f8549
[8.x] [ResponseOps][Connectors] Add connector filter in flyout (#211874) (#215365) 
# Backport

This will backport the following commits from `main` to `8.x`:
- [[ResponseOps][Connectors] Add connector filter in flyout
(#211874)](https://github.com/elastic/kibana/pull/211874)

<!--- Backport version: 9.6.6 -->

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

<!--BACKPORT [{"author":{"name":"Georgiana-Andreea
Onoleață","email":"georgiana.onoleata@elastic.co"},"sourceCommit":{"committedDate":"2025-03-20T16:06:00Z","message":"[ResponseOps][Connectors]
Add connector filter in flyout (#211874)\n\nCloses
https://github.com/elastic/kibana/issues/208001\n\n## Summary\n\n- Added
filtering option in the `create connector` flyout: \n\n- Search field:
\n - search connectors by name (or description)\n - cards dynamically
update based on the input\n - includes a clear button to reset the
search \n\n\nDemo:
\n\n\nhttps://github.com/user-attachments/assets/6d38a916-ad05-41dd-867e-c37260913067\n\n---------\n\nCo-authored-by:
Christos Nasikas <xristosnasikas@gmail.com>\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"2b96a82d4f2bf9967c2c36a2a571017779dd27a5","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["enhancement","release_note:skip","Team:ResponseOps","backport:version","v9.1.0","v8.19.0"],"title":"[ResponseOps][Connectors]
Add connector filter in
flyout","number":211874,"url":"https://github.com/elastic/kibana/pull/211874","mergeCommit":{"message":"[ResponseOps][Connectors]
Add connector filter in flyout (#211874)\n\nCloses
https://github.com/elastic/kibana/issues/208001\n\n## Summary\n\n- Added
filtering option in the `create connector` flyout: \n\n- Search field:
\n - search connectors by name (or description)\n - cards dynamically
update based on the input\n - includes a clear button to reset the
search \n\n\nDemo:
\n\n\nhttps://github.com/user-attachments/assets/6d38a916-ad05-41dd-867e-c37260913067\n\n---------\n\nCo-authored-by:
Christos Nasikas <xristosnasikas@gmail.com>\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"2b96a82d4f2bf9967c2c36a2a571017779dd27a5"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/211874","number":211874,"mergeCommit":{"message":"[ResponseOps][Connectors]
Add connector filter in flyout (#211874)\n\nCloses
https://github.com/elastic/kibana/issues/208001\n\n## Summary\n\n- Added
filtering option in the `create connector` flyout: \n\n- Search field:
\n - search connectors by name (or description)\n - cards dynamically
update based on the input\n - includes a clear button to reset the
search \n\n\nDemo:
\n\n\nhttps://github.com/user-attachments/assets/6d38a916-ad05-41dd-867e-c37260913067\n\n---------\n\nCo-authored-by:
Christos Nasikas <xristosnasikas@gmail.com>\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"2b96a82d4f2bf9967c2c36a2a571017779dd27a5"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Georgiana-Andreea Onoleață <georgiana.onoleata@elastic.co>
 2025-03-20 20:22:37 +02:00
Kibana Machine
3f0ede1ff6
[8.x] [ML] File upload minor design changes (#214539) (#215001) 
# Backport

This will backport the following commits from `main` to `8.x`:
- [[ML] File upload minor design changes
(#214539)](https://github.com/elastic/kibana/pull/214539)

<!--- Backport version: 9.6.6 -->

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

<!--BACKPORT [{"author":{"name":"James
Gowdy","email":"jgowdy@elastic.co"},"sourceCommit":{"committedDate":"2025-03-18T15:26:03Z","message":"[ML]
File upload minor design changes (#214539)\n\nDesign changes based
on\n[this](https://github.com/elastic/kibana/pull/213525#pullrequestreview-2684013527)\ncomment.\n\nPlaces
preview limit information into a callout.\nRemoves the \"Create new
index\" title.\nRemoves mention of ingest pipeline during upload
steps.\nAlso includes a fix for the preview of pdf
files.\n\n\n![image](https://github.com/user-attachments/assets/dbd25c54-032c-4596-9973-d4cd01cde364)","sha":"561151dfbb80c495ab2014139785e3110b0e2ef0","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":[":ml","release_note:skip","Feature:File
and Index Data Viz","Feature:File
Upload","backport:version","v9.1.0","v8.19.0"],"title":"[ML] File upload
minor design
changes","number":214539,"url":"https://github.com/elastic/kibana/pull/214539","mergeCommit":{"message":"[ML]
File upload minor design changes (#214539)\n\nDesign changes based
on\n[this](https://github.com/elastic/kibana/pull/213525#pullrequestreview-2684013527)\ncomment.\n\nPlaces
preview limit information into a callout.\nRemoves the \"Create new
index\" title.\nRemoves mention of ingest pipeline during upload
steps.\nAlso includes a fix for the preview of pdf
files.\n\n\n![image](https://github.com/user-attachments/assets/dbd25c54-032c-4596-9973-d4cd01cde364)","sha":"561151dfbb80c495ab2014139785e3110b0e2ef0"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/214539","number":214539,"mergeCommit":{"message":"[ML]
File upload minor design changes (#214539)\n\nDesign changes based
on\n[this](https://github.com/elastic/kibana/pull/213525#pullrequestreview-2684013527)\ncomment.\n\nPlaces
preview limit information into a callout.\nRemoves the \"Create new
index\" title.\nRemoves mention of ingest pipeline during upload
steps.\nAlso includes a fix for the preview of pdf
files.\n\n\n![image](https://github.com/user-attachments/assets/dbd25c54-032c-4596-9973-d4cd01cde364)","sha":"561151dfbb80c495ab2014139785e3110b0e2ef0"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: James Gowdy <jgowdy@elastic.co>
 2025-03-20 19:49:18 +02:00
Kibana Machine
dd0c2c7fe8
[8.x] [ES|QL] Make sure that the variables in the editor are always up to date (#214833) (#215362) 
# Backport

This will backport the following commits from `main` to `8.x`:
- [[ES|QL] Make sure that the variables in the editor are always up to
date (#214833)](https://github.com/elastic/kibana/pull/214833)

<!--- Backport version: 9.6.6 -->

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

<!--BACKPORT [{"author":{"name":"Stratoula
Kalafateli","email":"efstratia.kalafateli@elastic.co"},"sourceCommit":{"committedDate":"2025-03-20T15:33:22Z","message":"[ES|QL]
Make sure that the variables in the editor are always up to date
(#214833)\n\n## Summary\n\nCloses
https://github.com/elastic/kibana/issues/214663\n\nThe registry has the
updated
values.\n\n\n![meow](https://github.com/user-attachments/assets/134d0382-f198-4460-a66d-cce45d1208c5)","sha":"c63f2980fbfbf5df62c8e9eae08d84ff2789aa91","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Feature:ES|QL","Team:ESQL","backport:version","v9.1.0","v8.19.0"],"title":"[ES|QL]
Make sure that the variables in the editor are always up to
date","number":214833,"url":"https://github.com/elastic/kibana/pull/214833","mergeCommit":{"message":"[ES|QL]
Make sure that the variables in the editor are always up to date
(#214833)\n\n## Summary\n\nCloses
https://github.com/elastic/kibana/issues/214663\n\nThe registry has the
updated
values.\n\n\n![meow](https://github.com/user-attachments/assets/134d0382-f198-4460-a66d-cce45d1208c5)","sha":"c63f2980fbfbf5df62c8e9eae08d84ff2789aa91"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/214833","number":214833,"mergeCommit":{"message":"[ES|QL]
Make sure that the variables in the editor are always up to date
(#214833)\n\n## Summary\n\nCloses
https://github.com/elastic/kibana/issues/214663\n\nThe registry has the
updated
values.\n\n\n![meow](https://github.com/user-attachments/assets/134d0382-f198-4460-a66d-cce45d1208c5)","sha":"c63f2980fbfbf5df62c8e9eae08d84ff2789aa91"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Stratoula Kalafateli <efstratia.kalafateli@elastic.co>
 2025-03-20 19:31:33 +02:00
Kibana Machine
7b4412e0cb
[8.x] [Detection Engine] Rule Data View select uses Data View name for display (#214495) (#215354) 
# Backport

This will backport the following commits from `main` to `8.x`:
- [[Detection Engine] Rule Data View select uses Data View name for
display (#214495)](https://github.com/elastic/kibana/pull/214495)

<!--- Backport version: 9.6.6 -->

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

<!--BACKPORT [{"author":{"name":"Ryland
Herrick","email":"ryalnd@gmail.com"},"sourceCommit":{"committedDate":"2025-03-20T15:01:26Z","message":"[Detection
Engine] Rule Data View select uses Data View name for display
(#214495)\n\n## Summary\n\nSupersedes #190936, and also
addresses\nhttps://github.com/elastic/kibana/issues/137823. This mainly
just\nrebases the changes introduced there to the latest `main`. I
also\nnoticed that it originally had some unit tests, so I resurrected
those\nas well. ~~I modified the copy as well, so nota bene
@ARWNightingale~~\nAfter some discussion, we determined that an explicit
UI note about this\nbehavior was unnecessary.\n\n\n##
Screenshots\n\n<kbd>\n<img width=\"979\" alt=\"Screenshot 2025-03-13 at
5 24
42 PM\"\nsrc=\"https://github.com/user-attachments/assets/69da29bf-5504-461e-b797-d016adcd4b59\"\n/></kbd>\n\n<kbd><img
width=\"1052\" alt=\"Screenshot 2025-03-18 at 4 37
58 PM\"\nsrc=\"https://github.com/user-attachments/assets/8ee5e55e-2413-4936-aa87-7dadb3d7cbb1\"\n/></kbd>\n\n\n\n\n###
Checklist\n\n\n- [x] Any text added follows [EUI's
writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\nsentence case text and includes
[i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\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\n\n---------\n\nCo-authored-by: Yara Tercero
<yara.tercero@elastic.co>","sha":"07acd2480aea52d22a5c5454740cd2a1fa7a70e8","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:enhancement","Feature:Rule
Creation","backport:all-open","Team:Detection Engine","Feature:Rule
Edit","v9.1.0"],"title":"[Detection Engine] Rule Data View select uses
Data View name for
display","number":214495,"url":"https://github.com/elastic/kibana/pull/214495","mergeCommit":{"message":"[Detection
Engine] Rule Data View select uses Data View name for display
(#214495)\n\n## Summary\n\nSupersedes #190936, and also
addresses\nhttps://github.com/elastic/kibana/issues/137823. This mainly
just\nrebases the changes introduced there to the latest `main`. I
also\nnoticed that it originally had some unit tests, so I resurrected
those\nas well. ~~I modified the copy as well, so nota bene
@ARWNightingale~~\nAfter some discussion, we determined that an explicit
UI note about this\nbehavior was unnecessary.\n\n\n##
Screenshots\n\n<kbd>\n<img width=\"979\" alt=\"Screenshot 2025-03-13 at
5 24
42 PM\"\nsrc=\"https://github.com/user-attachments/assets/69da29bf-5504-461e-b797-d016adcd4b59\"\n/></kbd>\n\n<kbd><img
width=\"1052\" alt=\"Screenshot 2025-03-18 at 4 37
58 PM\"\nsrc=\"https://github.com/user-attachments/assets/8ee5e55e-2413-4936-aa87-7dadb3d7cbb1\"\n/></kbd>\n\n\n\n\n###
Checklist\n\n\n- [x] Any text added follows [EUI's
writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\nsentence case text and includes
[i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\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\n\n---------\n\nCo-authored-by: Yara Tercero
<yara.tercero@elastic.co>","sha":"07acd2480aea52d22a5c5454740cd2a1fa7a70e8"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/214495","number":214495,"mergeCommit":{"message":"[Detection
Engine] Rule Data View select uses Data View name for display
(#214495)\n\n## Summary\n\nSupersedes #190936, and also
addresses\nhttps://github.com/elastic/kibana/issues/137823. This mainly
just\nrebases the changes introduced there to the latest `main`. I
also\nnoticed that it originally had some unit tests, so I resurrected
those\nas well. ~~I modified the copy as well, so nota bene
@ARWNightingale~~\nAfter some discussion, we determined that an explicit
UI note about this\nbehavior was unnecessary.\n\n\n##
Screenshots\n\n<kbd>\n<img width=\"979\" alt=\"Screenshot 2025-03-13 at
5 24
42 PM\"\nsrc=\"https://github.com/user-attachments/assets/69da29bf-5504-461e-b797-d016adcd4b59\"\n/></kbd>\n\n<kbd><img
width=\"1052\" alt=\"Screenshot 2025-03-18 at 4 37
58 PM\"\nsrc=\"https://github.com/user-attachments/assets/8ee5e55e-2413-4936-aa87-7dadb3d7cbb1\"\n/></kbd>\n\n\n\n\n###
Checklist\n\n\n- [x] Any text added follows [EUI's
writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\nsentence case text and includes
[i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\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\n\n---------\n\nCo-authored-by: Yara Tercero
<yara.tercero@elastic.co>","sha":"07acd2480aea52d22a5c5454740cd2a1fa7a70e8"}}]}]
BACKPORT-->

Co-authored-by: Ryland Herrick <ryalnd@gmail.com>
 2025-03-20 19:06:42 +02:00
Kibana Machine
986efdc610
[8.x] [SecuritySolution] Fix Data view refresh does not support the indexPattern parameter (#215151) (#215347) 
# Backport

This will backport the following commits from `main` to `8.x`:
- [[SecuritySolution] Fix Data view refresh does not support the
indexPattern parameter
(#215151)](https://github.com/elastic/kibana/pull/215151)

<!--- Backport version: 9.6.6 -->

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

<!--BACKPORT [{"author":{"name":"Pablo
Machado","email":"pablo.nevesmachado@elastic.co"},"sourceCommit":{"committedDate":"2025-03-20T14:41:54Z","message":"[SecuritySolution]
Fix Data view refresh does not support the indexPattern parameter
(#215151)\n\n## Summary\n\nWhen the data view refresh API or task was
executed, it was overwriting\nthe engine's additional
`indexPattern`.\n\nThis PR updates the code to support `indexPattern`
and ensures the user\nhas privileges for all indices.\n\nI extracted the
merge function to add deduplicate logic.\n\n### How to reproduce it?\n*
Create an entity store using the indexPatterns param\n* Call refresh
dataview API
(`POST\nkbn:api/entity_store/engines/apply_dataview_indices`)\n* It will
apply the dataview and ignore the indexPatterns param\n\nAfter the fix,
we should be able to update the indexPatterns param, and\nthe task that
refreshes the index pattern should pick up the
change\nproperly.\n\n\n### Checklist\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":"42183d6039c1bb71b42642747f88493fbe591c2e","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix","v9.0.0","Team:
SecuritySolution","Theme: entity_analytics","Feature:Entity
Analytics","Team:Entity
Analytics","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[SecuritySolution]
Fix Data view refresh does not support the indexPattern
parameter","number":215151,"url":"https://github.com/elastic/kibana/pull/215151","mergeCommit":{"message":"[SecuritySolution]
Fix Data view refresh does not support the indexPattern parameter
(#215151)\n\n## Summary\n\nWhen the data view refresh API or task was
executed, it was overwriting\nthe engine's additional
`indexPattern`.\n\nThis PR updates the code to support `indexPattern`
and ensures the user\nhas privileges for all indices.\n\nI extracted the
merge function to add deduplicate logic.\n\n### How to reproduce it?\n*
Create an entity store using the indexPatterns param\n* Call refresh
dataview API
(`POST\nkbn:api/entity_store/engines/apply_dataview_indices`)\n* It will
apply the dataview and ignore the indexPatterns param\n\nAfter the fix,
we should be able to update the indexPatterns param, and\nthe task that
refreshes the index pattern should pick up the
change\nproperly.\n\n\n### Checklist\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":"42183d6039c1bb71b42642747f88493fbe591c2e"}},"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/215151","number":215151,"mergeCommit":{"message":"[SecuritySolution]
Fix Data view refresh does not support the indexPattern parameter
(#215151)\n\n## Summary\n\nWhen the data view refresh API or task was
executed, it was overwriting\nthe engine's additional
`indexPattern`.\n\nThis PR updates the code to support `indexPattern`
and ensures the user\nhas privileges for all indices.\n\nI extracted the
merge function to add deduplicate logic.\n\n### How to reproduce it?\n*
Create an entity store using the indexPatterns param\n* Call refresh
dataview API
(`POST\nkbn:api/entity_store/engines/apply_dataview_indices`)\n* It will
apply the dataview and ignore the indexPatterns param\n\nAfter the fix,
we should be able to update the indexPatterns param, and\nthe task that
refreshes the index pattern should pick up the
change\nproperly.\n\n\n### Checklist\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":"42183d6039c1bb71b42642747f88493fbe591c2e"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Pablo Machado <pablo.nevesmachado@elastic.co>
 2025-03-20 18:53:36 +02:00
Kibana Machine
a8da56b01e
[8.x] [ML] Anomaly Explorer: Migrate Explorer from SCSS to Emotion (#215196) (#215350) 
# Backport

This will backport the following commits from `main` to `8.x`:
- [[ML] Anomaly Explorer: Migrate Explorer from SCSS to Emotion
(#215196)](https://github.com/elastic/kibana/pull/215196)

<!--- Backport version: 9.6.6 -->

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

<!--BACKPORT [{"author":{"name":"Robert
Jaszczurek","email":"92210485+rbrtj@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-20T14:50:45Z","message":"[ML]
Anomaly Explorer: Migrate Explorer from SCSS to Emotion
(#215196)\n\nMigrate remaining Anomaly Explorer styles from SCSS to
Emotion:\n\n| Before | After |\n| ------------- | ------------- |\n|
Anomaly Swimlane | Anomaly Swimlane | \n| <img width=\"983\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/d654bf74-f04a-4f57-8891-af0c0a0d3b85\"\n/>
| <img width=\"824\" alt=\"Pasted Graphic
1\"\nsrc=\"https://github.com/user-attachments/assets/38e00adf-dba1-43be-a6da-6141221dc82b\"\n/>
|\n| Swimlane embeddable | Swimlane embeddable |\n| <img width=\"573\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/304d0073-a194-41cd-a379-5fc1fbb734a6\"\n/>
| <img width=\"580\" alt=\"Create
visualization\"\nsrc=\"https://github.com/user-attachments/assets/28982191-16c1-437d-9955-77ca73fbe4f0\"\n/>
|\n| Anomalies charts tooltip and label | Anomalies charts tooltip
and\nlabel |\n| <img width=\"970\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/f6cb53f3-b79e-4eac-84c2-18d1d0a53cc0\"\n/>
| <img width=\"974\" alt=\"Pasted Graphic
3\"\nsrc=\"https://github.com/user-attachments/assets/2f553118-8c4f-4678-809d-f7f25816fb1c\"\n/>
|","sha":"14c6204dca2499a9c45ba0a319c45f40ff531c4e","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["chore",":ml","release_note:skip","Team:ML","backport:version","v9.1.0","v8.19.0"],"title":"[ML]
Anomaly Explorer: Migrate Explorer from SCSS to
Emotion","number":215196,"url":"https://github.com/elastic/kibana/pull/215196","mergeCommit":{"message":"[ML]
Anomaly Explorer: Migrate Explorer from SCSS to Emotion
(#215196)\n\nMigrate remaining Anomaly Explorer styles from SCSS to
Emotion:\n\n| Before | After |\n| ------------- | ------------- |\n|
Anomaly Swimlane | Anomaly Swimlane | \n| <img width=\"983\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/d654bf74-f04a-4f57-8891-af0c0a0d3b85\"\n/>
| <img width=\"824\" alt=\"Pasted Graphic
1\"\nsrc=\"https://github.com/user-attachments/assets/38e00adf-dba1-43be-a6da-6141221dc82b\"\n/>
|\n| Swimlane embeddable | Swimlane embeddable |\n| <img width=\"573\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/304d0073-a194-41cd-a379-5fc1fbb734a6\"\n/>
| <img width=\"580\" alt=\"Create
visualization\"\nsrc=\"https://github.com/user-attachments/assets/28982191-16c1-437d-9955-77ca73fbe4f0\"\n/>
|\n| Anomalies charts tooltip and label | Anomalies charts tooltip
and\nlabel |\n| <img width=\"970\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/f6cb53f3-b79e-4eac-84c2-18d1d0a53cc0\"\n/>
| <img width=\"974\" alt=\"Pasted Graphic
3\"\nsrc=\"https://github.com/user-attachments/assets/2f553118-8c4f-4678-809d-f7f25816fb1c\"\n/>
|","sha":"14c6204dca2499a9c45ba0a319c45f40ff531c4e"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/215196","number":215196,"mergeCommit":{"message":"[ML]
Anomaly Explorer: Migrate Explorer from SCSS to Emotion
(#215196)\n\nMigrate remaining Anomaly Explorer styles from SCSS to
Emotion:\n\n| Before | After |\n| ------------- | ------------- |\n|
Anomaly Swimlane | Anomaly Swimlane | \n| <img width=\"983\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/d654bf74-f04a-4f57-8891-af0c0a0d3b85\"\n/>
| <img width=\"824\" alt=\"Pasted Graphic
1\"\nsrc=\"https://github.com/user-attachments/assets/38e00adf-dba1-43be-a6da-6141221dc82b\"\n/>
|\n| Swimlane embeddable | Swimlane embeddable |\n| <img width=\"573\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/304d0073-a194-41cd-a379-5fc1fbb734a6\"\n/>
| <img width=\"580\" alt=\"Create
visualization\"\nsrc=\"https://github.com/user-attachments/assets/28982191-16c1-437d-9955-77ca73fbe4f0\"\n/>
|\n| Anomalies charts tooltip and label | Anomalies charts tooltip
and\nlabel |\n| <img width=\"970\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/f6cb53f3-b79e-4eac-84c2-18d1d0a53cc0\"\n/>
| <img width=\"974\" alt=\"Pasted Graphic
3\"\nsrc=\"https://github.com/user-attachments/assets/2f553118-8c4f-4678-809d-f7f25816fb1c\"\n/>
|","sha":"14c6204dca2499a9c45ba0a319c45f40ff531c4e"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Robert Jaszczurek <92210485+rbrtj@users.noreply.github.com>
 2025-03-20 18:45:15 +02:00
florent-leborgne
2d55dc77d8
[Docs] Add 8.18.0 release notes and what's new page (#212637) 
This PR adds release notes and what's new changes for the 8.18.0
release.

This PR will remain in draft mode until the following are completed:

- [x] Generate raw changelog content
- [x] Initial clean up of changelog content
- [x] Add What's new page content
- [x] Styling edits in what's new page content

## Previews links

- What's new:
https://kibana_bk_212637.docs-preview.app.elstc.co/guide/en/kibana/8.x/whats-new.html
- Release notes:
https://kibana_bk_212637.docs-preview.app.elstc.co/guide/en/kibana/8.x/release-notes-8.18.0.html
and sub pages

---------

Co-authored-by: wajihaparvez <wajiha.parvez@elastic.co>
Co-authored-by: Matthias Wilhelm <ankertal@gmail.com>
Co-authored-by: Marco Vettorello <vettorello.marco@gmail.com>
 2025-03-20 16:52:01 +01:00
Kibana Machine
b8ed0c3060
[8.x] [Synthetics] Retries journeys on failures !! (#215264) (#215310) 
# Backport

This will backport the following commits from `main` to `8.x`:
- [[Synthetics] Retries journeys on failures !!
(#215264)](https://github.com/elastic/kibana/pull/215264)

<!--- Backport version: 9.6.6 -->

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

<!--BACKPORT
[{"author":{"name":"Shahzad","email":"shahzad31comp@gmail.com"},"sourceCommit":{"committedDate":"2025-03-20T10:53:55Z","message":"[Synthetics]
Retries journeys on failures !! (#215264)\n\n## Summary\n\nRetries
journeys on failures
!!","sha":"0dad68dce78a21b74e5a946e494f8d2bf81c6822","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:version","v8.18.0","ci:synthetics-runner-suites","v9.1.0","v8.19.0"],"title":"[Synthetics]
Retries journeys on failures
!!","number":215264,"url":"https://github.com/elastic/kibana/pull/215264","mergeCommit":{"message":"[Synthetics]
Retries journeys on failures !! (#215264)\n\n## Summary\n\nRetries
journeys on failures
!!","sha":"0dad68dce78a21b74e5a946e494f8d2bf81c6822"}},"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/215264","number":215264,"mergeCommit":{"message":"[Synthetics]
Retries journeys on failures !! (#215264)\n\n## Summary\n\nRetries
journeys on failures
!!","sha":"0dad68dce78a21b74e5a946e494f8d2bf81c6822"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Shahzad <shahzad31comp@gmail.com>
 2025-03-20 14:44:18 +02:00
Kibana Machine
a1a872b8cb
[8.x] Upgrade axios 1.8.3 in buildkite (#215203) (#215297) 
# Backport

This will backport the following commits from `main` to `8.x`:
- [Upgrade axios 1.8.3 in buildkite
(#215203)](https://github.com/elastic/kibana/pull/215203)

<!--- Backport version: 9.6.6 -->

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

<!--BACKPORT [{"author":{"name":"Alex
Szabo","email":"alex.szabo@elastic.co"},"sourceCommit":{"committedDate":"2025-03-20T09:58:41Z","message":"Upgrade
axios 1.8.3 in buildkite (#215203)\n\n## Summary\nUpgrade `axios` to
1.8.3 in Kibana's `.buildkite` subproject; disallow\nabsolute URLs in
axios
clients.","sha":"d8f6bd694b5004547623f506b3a3497bb556c2a1","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Operations","release_note:skip","backport:all-open","v9.1.0"],"title":"Upgrade
axios 1.8.3 in
buildkite","number":215203,"url":"https://github.com/elastic/kibana/pull/215203","mergeCommit":{"message":"Upgrade
axios 1.8.3 in buildkite (#215203)\n\n## Summary\nUpgrade `axios` to
1.8.3 in Kibana's `.buildkite` subproject; disallow\nabsolute URLs in
axios
clients.","sha":"d8f6bd694b5004547623f506b3a3497bb556c2a1"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/215203","number":215203,"mergeCommit":{"message":"Upgrade
axios 1.8.3 in buildkite (#215203)\n\n## Summary\nUpgrade `axios` to
1.8.3 in Kibana's `.buildkite` subproject; disallow\nabsolute URLs in
axios clients.","sha":"d8f6bd694b5004547623f506b3a3497bb556c2a1"}}]}]
BACKPORT-->

Co-authored-by: Alex Szabo <alex.szabo@elastic.co>
 2025-03-20 13:54:38 +02:00
Kibana Machine
5b0fba9a01
[8.x] [Security Solution][Defend Workflows] Enables endpoint integrations FTR tests (#214120) (#215289) 
# Backport

This will backport the following commits from `main` to `8.x`:
- [[Security Solution][Defend Workflows] Enables endpoint integrations
FTR tests (#214120)](https://github.com/elastic/kibana/pull/214120)

<!--- Backport version: 9.6.6 -->

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

<!--BACKPORT [{"author":{"name":"David
Sánchez","email":"david.sanchezsoler@elastic.co"},"sourceCommit":{"committedDate":"2025-03-20T09:37:11Z","message":"[Security
Solution][Defend Workflows] Enables endpoint integrations FTR tests
(#214120)\n\n## Summary\n\nEnables endpoint integrations ftr
test.\n\ncloses:
https://github.com/elastic/kibana/issues/203916\n\nCo-authored-by:
Elastic Machine
<elasticmachine@users.noreply.github.com>","sha":"1119bf187dc04e130c3df610b5fdeb7301e40311","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Defend
Workflows","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Security
Solution][Defend Workflows] Enables endpoint integrations FTR
tests","number":214120,"url":"https://github.com/elastic/kibana/pull/214120","mergeCommit":{"message":"[Security
Solution][Defend Workflows] Enables endpoint integrations FTR tests
(#214120)\n\n## Summary\n\nEnables endpoint integrations ftr
test.\n\ncloses:
https://github.com/elastic/kibana/issues/203916\n\nCo-authored-by:
Elastic Machine
<elasticmachine@users.noreply.github.com>","sha":"1119bf187dc04e130c3df610b5fdeb7301e40311"}},"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/214120","number":214120,"mergeCommit":{"message":"[Security
Solution][Defend Workflows] Enables endpoint integrations FTR tests
(#214120)\n\n## Summary\n\nEnables endpoint integrations ftr
test.\n\ncloses:
https://github.com/elastic/kibana/issues/203916\n\nCo-authored-by:
Elastic Machine
<elasticmachine@users.noreply.github.com>","sha":"1119bf187dc04e130c3df610b5fdeb7301e40311"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: David Sánchez <david.sanchezsoler@elastic.co>
 2025-03-20 13:39:17 +02:00
Kibana Machine
2d8b76bb48
[8.x] chore(security,codeql): exclude more dev/test folders from CodeQL scans (#215303) (#215316) 
# Backport

This will backport the following commits from `main` to `8.x`:
- [chore(security,codeql): exclude more dev/test folders from CodeQL
scans (#215303)](https://github.com/elastic/kibana/pull/215303)

<!--- Backport version: 9.6.6 -->

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

<!--BACKPORT [{"author":{"name":"Aleh
Zasypkin","email":"aleh.zasypkin@elastic.co"},"sourceCommit":{"committedDate":"2025-03-20T11:05:16Z","message":"chore(security,codeql):
exclude more dev/test folders from CodeQL scans (#215303)\n\n##
Summary\n\nExclude more dev/test folders from CodeQL
scans","sha":"38de01504bac45f793d59b9c135dc18b2ecf7199","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["chore","release_note:skip","security","v9.0.0","backport:version","v9.1.0","v8.19.0"],"title":"chore(security,codeql):
exclude more dev/test folders from CodeQL
scans","number":215303,"url":"https://github.com/elastic/kibana/pull/215303","mergeCommit":{"message":"chore(security,codeql):
exclude more dev/test folders from CodeQL scans (#215303)\n\n##
Summary\n\nExclude more dev/test folders from CodeQL
scans","sha":"38de01504bac45f793d59b9c135dc18b2ecf7199"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.x"],"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/215303","number":215303,"mergeCommit":{"message":"chore(security,codeql):
exclude more dev/test folders from CodeQL scans (#215303)\n\n##
Summary\n\nExclude more dev/test folders from CodeQL
scans","sha":"38de01504bac45f793d59b9c135dc18b2ecf7199"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Aleh Zasypkin <aleh.zasypkin@elastic.co>
 2025-03-20 11:34:38 +00:00
Kibana Machine
b6e09a83f7
[8.x] Fix APM URLs in doc link service (#215261) (#215283) 
# Backport

This will backport the following commits from `main` to `8.x`:
- [Fix APM URLs in doc link service
(#215261)](https://github.com/elastic/kibana/pull/215261)

<!--- Backport version: 9.6.6 -->

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

<!--BACKPORT [{"author":{"name":"Lisa
Cawley","email":"lcawley@elastic.co"},"sourceCommit":{"committedDate":"2025-03-20T09:00:12Z","message":"Fix
APM URLs in doc link service
(#215261)","sha":"dcbefc3b27fc6733d0776ad371f5b2e4b0ad9e6e","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Docs","release_note:skip","docs","backport:version","v9.1.0","v8.19.0","v8.18.1","v9.0.1"],"title":"Fix
APM URLs in doc link
service","number":215261,"url":"https://github.com/elastic/kibana/pull/215261","mergeCommit":{"message":"Fix
APM URLs in doc link service
(#215261)","sha":"dcbefc3b27fc6733d0776ad371f5b2e4b0ad9e6e"}},"sourceBranch":"main","suggestedTargetBranches":["8.x","8.18","9.0"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/215261","number":215261,"mergeCommit":{"message":"Fix
APM URLs in doc link service
(#215261)","sha":"dcbefc3b27fc6733d0776ad371f5b2e4b0ad9e6e"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Lisa Cawley <lcawley@elastic.co>
 2025-03-20 12:48:04 +02:00
Kerry Gallagher
e7d1c9215e
[8.x] [Streams] [Dedicated Grok UI] Package / highlight matched parts / suggestions (#213278) (#215204) 
# Backport

This will backport the following commits from `main` to `8.x`:
- [[Streams] [Dedicated Grok UI] Package / highlight matched parts /
suggestions (#213278)](https://github.com/elastic/kibana/pull/213278)

<!--- Backport version: 9.6.6 -->

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

<!--BACKPORT [{"author":{"name":"Kerry
Gallagher","email":"kerry.gallagher@elastic.co"},"sourceCommit":{"committedDate":"2025-03-18T22:56:58Z","message":"[Streams]
[Dedicated Grok UI] Package / highlight matched parts / suggestions
(#213278)\n\n## Summary\n\nCloses
https://github.com/elastic/streams-program/issues/170
and\nhttps://github.com/elastic/streams-program/issues/171\n\n##
Reviewer notes\n\nIt's worth reading the research
in\nhttps://github.com/elastic/streams-program/issues/168 to understand
why\ncertain decisions were made. Some of the resolving code is inspired
by\n`grok-js`, unfortunately this wasn't something we could use
directly.\n\nThe design / UX is **not** final. This is just a functional
version. The\neditor is currently on the streams > enrichment page so it
can be played\nwith, this will **not** be merged.\n\nThere is pattern
support for our ECS patterns, I have not added the\nlegacy
ones.\n\nThere will almost certainly be some edge cases that don't work,
every\nrepo for a Grok tool I looked at had their own 😅 I've tried to
test this\nwith lots of varied examples though.\n\nI'd recommend
unticking \"No extension\" from the file filter to remove\nthe pattern
files.\n\n<img width=\"323\" alt=\"Screenshot 2025-03-06 at 22 40
19\"\nsrc=\"https://github.com/user-attachments/assets/5b594f5f-0b0f-4ed0-ae10-2412fcf9e31a\"\n/>\n\n##
Possible improvements / followups\n\n- We could in the future expand the
UI to toggle on and off certain\npattern collections.\n\n- Ability to
add custom patterns (like in our Grok debugger). This can\nstill be
achieved with `(?<queue_id>[0-9A-F]{10,11})` syntax.\n\n- Point out when
regex is invalid (right now it's silent).\n\n- I've copied over the
patterns from the ES repo for now, with a light\nscript to generate an
object from them. There's a CLI skeleton in place\nif we feel we want to
actually pull these from the ES repo directly.\nThese patterns don't
change often, and aren't heavy size wise.\n\n- Debouncing etc for
processing, but I'd like to see how the final UX\nends up.\n\n##
Media\n\nScreenshot\n\n![Screenshot 2025-03-06 at 11
58\n56](https://github.com/user-attachments/assets/158b2a6f-df26-490e-b9f8-63ae69625607)\n\nSimple
example\n\n\n![simple_example](https://github.com/user-attachments/assets/36f36505-eb0b-45d6-bd24-1dbef769658d)\n\nComplex
example\n\n\n![complex_example](https://github.com/user-attachments/assets/968cc935-d208-4ef0-a64d-452995dccd5e)\n\n---------\n\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"f9783504bbc9993027967c36cdcfb8d2a37bddfb","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:version","Feature:Streams","v9.1.0","v8.19.0"],"title":"[Streams]
[Dedicated Grok UI] Package / highlight matched parts /
suggestions","number":213278,"url":"https://github.com/elastic/kibana/pull/213278","mergeCommit":{"message":"[Streams]
[Dedicated Grok UI] Package / highlight matched parts / suggestions
(#213278)\n\n## Summary\n\nCloses
https://github.com/elastic/streams-program/issues/170
and\nhttps://github.com/elastic/streams-program/issues/171\n\n##
Reviewer notes\n\nIt's worth reading the research
in\nhttps://github.com/elastic/streams-program/issues/168 to understand
why\ncertain decisions were made. Some of the resolving code is inspired
by\n`grok-js`, unfortunately this wasn't something we could use
directly.\n\nThe design / UX is **not** final. This is just a functional
version. The\neditor is currently on the streams > enrichment page so it
can be played\nwith, this will **not** be merged.\n\nThere is pattern
support for our ECS patterns, I have not added the\nlegacy
ones.\n\nThere will almost certainly be some edge cases that don't work,
every\nrepo for a Grok tool I looked at had their own 😅 I've tried to
test this\nwith lots of varied examples though.\n\nI'd recommend
unticking \"No extension\" from the file filter to remove\nthe pattern
files.\n\n<img width=\"323\" alt=\"Screenshot 2025-03-06 at 22 40
19\"\nsrc=\"https://github.com/user-attachments/assets/5b594f5f-0b0f-4ed0-ae10-2412fcf9e31a\"\n/>\n\n##
Possible improvements / followups\n\n- We could in the future expand the
UI to toggle on and off certain\npattern collections.\n\n- Ability to
add custom patterns (like in our Grok debugger). This can\nstill be
achieved with `(?<queue_id>[0-9A-F]{10,11})` syntax.\n\n- Point out when
regex is invalid (right now it's silent).\n\n- I've copied over the
patterns from the ES repo for now, with a light\nscript to generate an
object from them. There's a CLI skeleton in place\nif we feel we want to
actually pull these from the ES repo directly.\nThese patterns don't
change often, and aren't heavy size wise.\n\n- Debouncing etc for
processing, but I'd like to see how the final UX\nends up.\n\n##
Media\n\nScreenshot\n\n![Screenshot 2025-03-06 at 11
58\n56](https://github.com/user-attachments/assets/158b2a6f-df26-490e-b9f8-63ae69625607)\n\nSimple
example\n\n\n![simple_example](https://github.com/user-attachments/assets/36f36505-eb0b-45d6-bd24-1dbef769658d)\n\nComplex
example\n\n\n![complex_example](https://github.com/user-attachments/assets/968cc935-d208-4ef0-a64d-452995dccd5e)\n\n---------\n\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"f9783504bbc9993027967c36cdcfb8d2a37bddfb"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/213278","number":213278,"mergeCommit":{"message":"[Streams]
[Dedicated Grok UI] Package / highlight matched parts / suggestions
(#213278)\n\n## Summary\n\nCloses
https://github.com/elastic/streams-program/issues/170
and\nhttps://github.com/elastic/streams-program/issues/171\n\n##
Reviewer notes\n\nIt's worth reading the research
in\nhttps://github.com/elastic/streams-program/issues/168 to understand
why\ncertain decisions were made. Some of the resolving code is inspired
by\n`grok-js`, unfortunately this wasn't something we could use
directly.\n\nThe design / UX is **not** final. This is just a functional
version. The\neditor is currently on the streams > enrichment page so it
can be played\nwith, this will **not** be merged.\n\nThere is pattern
support for our ECS patterns, I have not added the\nlegacy
ones.\n\nThere will almost certainly be some edge cases that don't work,
every\nrepo for a Grok tool I looked at had their own 😅 I've tried to
test this\nwith lots of varied examples though.\n\nI'd recommend
unticking \"No extension\" from the file filter to remove\nthe pattern
files.\n\n<img width=\"323\" alt=\"Screenshot 2025-03-06 at 22 40
19\"\nsrc=\"https://github.com/user-attachments/assets/5b594f5f-0b0f-4ed0-ae10-2412fcf9e31a\"\n/>\n\n##
Possible improvements / followups\n\n- We could in the future expand the
UI to toggle on and off certain\npattern collections.\n\n- Ability to
add custom patterns (like in our Grok debugger). This can\nstill be
achieved with `(?<queue_id>[0-9A-F]{10,11})` syntax.\n\n- Point out when
regex is invalid (right now it's silent).\n\n- I've copied over the
patterns from the ES repo for now, with a light\nscript to generate an
object from them. There's a CLI skeleton in place\nif we feel we want to
actually pull these from the ES repo directly.\nThese patterns don't
change often, and aren't heavy size wise.\n\n- Debouncing etc for
processing, but I'd like to see how the final UX\nends up.\n\n##
Media\n\nScreenshot\n\n![Screenshot 2025-03-06 at 11
58\n56](https://github.com/user-attachments/assets/158b2a6f-df26-490e-b9f8-63ae69625607)\n\nSimple
example\n\n\n![simple_example](https://github.com/user-attachments/assets/36f36505-eb0b-45d6-bd24-1dbef769658d)\n\nComplex
example\n\n\n![complex_example](https://github.com/user-attachments/assets/968cc935-d208-4ef0-a64d-452995dccd5e)\n\n---------\n\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"f9783504bbc9993027967c36cdcfb8d2a37bddfb"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
 2025-03-20 11:45:29 +01:00