2892 commits

Author	SHA1	Message	Date
Aleh Zasypkin	1d08980636	[8.6] Ensure that API keys are rendered before performing bulk delete in functional tests. (#148013) (#148044) ... # Backport This will backport the following commits from `main` to `8.6`: - [Ensure that API keys are rendered before performing bulk delete in functional tests. (#148013)](https://github.com/elastic/kibana/pull/148013) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Aleh Zasypkin","email":"aleh.zasypkin@elastic.co"},"sourceCommit":{"committedDate":"2022-12-22T18:44:11Z","message":"Ensure that API keys are rendered before performing bulk delete in functional tests. (#148013)","sha":"3a5f5626b2c3631eb2646782937171d2f87ce525","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["test","Team:Security","Feature:Users/Roles/API Keys","release_note:skip","ci:no-auto-commit","backport:all-open","v8.7.0"],"number":148013,"url":"https://github.com/elastic/kibana/pull/148013","mergeCommit":{"message":"Ensure that API keys are rendered before performing bulk delete in functional tests. (#148013)","sha":"3a5f5626b2c3631eb2646782937171d2f87ce525"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/148013","number":148013,"mergeCommit":{"message":"Ensure that API keys are rendered before performing bulk delete in functional tests. (#148013)","sha":"3a5f5626b2c3631eb2646782937171d2f87ce525"}}]}] BACKPORT-->	2022-12-23 03:12:58 -07:00
Walter Rafelsberger	32265b766d	[8.6] [ML] Explain Log Rate Spikes: Fix client side code to transform groups into table rows. (#147592) (#147832) ... # Backport This will backport the following commits from `main` to `8.6`: - [[ML] Explain Log Rate Spikes: Fix client side code to transform groups into table rows. (#147592)](https://github.com/elastic/kibana/pull/147592) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Walter Rafelsberger","email":"walter.rafelsberger@elastic.co"},"sourceCommit":{"committedDate":"2022-12-20T08:19:11Z","message":"[ML] Explain Log Rate Spikes: Fix client side code to transform groups into table rows. (#147592)\n\nFixes client side code to transform groups into table rows. Because the\r\ntransformation used a dictionary like structure with field names as\r\nkeys, we missed if there were multiple values for a field. This changes\r\nthe structure to an array of field/value pairs so we can support\r\nmultiple values per field.","sha":"92ffe2764f01a67658db854506bbd5003f0adcb8","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix",":ml","Feature:ML/AIOps","v8.6.0","v8.7.0"],"number":147592,"url":"https://github.com/elastic/kibana/pull/147592","mergeCommit":{"message":"[ML] Explain Log Rate Spikes: Fix client side code to transform groups into table rows. (#147592)\n\nFixes client side code to transform groups into table rows. Because the\r\ntransformation used a dictionary like structure with field names as\r\nkeys, we missed if there were multiple values for a field. This changes\r\nthe structure to an array of field/value pairs so we can support\r\nmultiple values per field.","sha":"92ffe2764f01a67658db854506bbd5003f0adcb8"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/147592","number":147592,"mergeCommit":{"message":"[ML] Explain Log Rate Spikes: Fix client side code to transform groups into table rows. (#147592)\n\nFixes client side code to transform groups into table rows. Because the\r\ntransformation used a dictionary like structure with field names as\r\nkeys, we missed if there were multiple values for a field. This changes\r\nthe structure to an array of field/value pairs so we can support\r\nmultiple values per field.","sha":"92ffe2764f01a67658db854506bbd5003f0adcb8"}}]}] BACKPORT-->	2022-12-20 02:39:02 -07:00
Kibana Machine	47066b37dc	[8.6] [ML] Explain Log Rate Spikes: Fix field candidate selection. (#147614) (#147792) ... # Backport This will backport the following commits from `main` to `8.6`: - [[ML] Explain Log Rate Spikes: Fix field candidate selection. (#147614)](https://github.com/elastic/kibana/pull/147614) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Walter Rafelsberger","email":"walter.rafelsberger@elastic.co"},"sourceCommit":{"committedDate":"2022-12-19T17:35:31Z","message":"[ML] Explain Log Rate Spikes: Fix field candidate selection. (#147614)\n\nThe field candidate selection for Explain Log Rate Spikes was missing a\r\ncheck if the supported field type is also aggregatable. For example, a\r\n`keyword` type field could still be non-aggregatable if it was both not\r\nindexed and `doc_values` set to `false`. Additionally, if no groups were\r\ndetected, we showed a \"Try to continue analysis\" button in the UI even\r\nif the analysis was able to finish. In this PR the artificial logs dataset for functional tests was extended\r\nto include a field like that.","sha":"aecad27159764d8ea2d0aeddc94fd03954d480e5","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix",":ml","Feature:ML/AIOps","v8.6.0","v8.7.0"],"number":147614,"url":"https://github.com/elastic/kibana/pull/147614","mergeCommit":{"message":"[ML] Explain Log Rate Spikes: Fix field candidate selection. (#147614)\n\nThe field candidate selection for Explain Log Rate Spikes was missing a\r\ncheck if the supported field type is also aggregatable. For example, a\r\n`keyword` type field could still be non-aggregatable if it was both not\r\nindexed and `doc_values` set to `false`. Additionally, if no groups were\r\ndetected, we showed a \"Try to continue analysis\" button in the UI even\r\nif the analysis was able to finish. In this PR the artificial logs dataset for functional tests was extended\r\nto include a field like that.","sha":"aecad27159764d8ea2d0aeddc94fd03954d480e5"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/147614","number":147614,"mergeCommit":{"message":"[ML] Explain Log Rate Spikes: Fix field candidate selection. (#147614)\n\nThe field candidate selection for Explain Log Rate Spikes was missing a\r\ncheck if the supported field type is also aggregatable. For example, a\r\n`keyword` type field could still be non-aggregatable if it was both not\r\nindexed and `doc_values` set to `false`. Additionally, if no groups were\r\ndetected, we showed a \"Try to continue analysis\" button in the UI even\r\nif the analysis was able to finish. In this PR the artificial logs dataset for functional tests was extended\r\nto include a field like that.","sha":"aecad27159764d8ea2d0aeddc94fd03954d480e5"}}]}] BACKPORT--> Co-authored-by: Walter Rafelsberger <walter.rafelsberger@elastic.co>	2022-12-19 12:06:34 -07:00
Dmitry Tomashevich	66d0f5590d	[8.6] [Discover] Fix Discover navigation from Lens embeddable (#147000) (#147608) ... # Backport This will backport the following commits from `main` to `8.6`: - [[Discover] Fix Discover navigation from Lens embeddable (#147000)](https://github.com/elastic/kibana/pull/147000) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Dmitry Tomashevich","email":"39378793+dimaanj@users.noreply.github.com"},"sourceCommit":{"committedDate":"2022-12-14T13:17:17Z","message":"[Discover] Fix Discover navigation from Lens embeddable (#147000)\n\n## Summary\r\n\r\nFixes #146761\r\n\r\nThis PR fixes navigation to Discover from Lens embeddable.\r\n\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n\r\nCo-authored-by: Marco Liberati <dej611@users.noreply.github.com>","sha":"1f04bf89a3df377c79dba225dd47c9a96dc3e395","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Discover","release_note:fix","auto-backport","Team:DataDiscovery","v8.7.0","v8.6.1"],"number":147000,"url":"https://github.com/elastic/kibana/pull/147000","mergeCommit":{"message":"[Discover] Fix Discover navigation from Lens embeddable (#147000)\n\n## Summary\r\n\r\nFixes #146761\r\n\r\nThis PR fixes navigation to Discover from Lens embeddable.\r\n\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n\r\nCo-authored-by: Marco Liberati <dej611@users.noreply.github.com>","sha":"1f04bf89a3df377c79dba225dd47c9a96dc3e395"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/147000","number":147000,"mergeCommit":{"message":"[Discover] Fix Discover navigation from Lens embeddable (#147000)\n\n## Summary\r\n\r\nFixes #146761\r\n\r\nThis PR fixes navigation to Discover from Lens embeddable.\r\n\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n\r\nCo-authored-by: Marco Liberati <dej611@users.noreply.github.com>","sha":"1f04bf89a3df377c79dba225dd47c9a96dc3e395"}},{"branch":"8.6","label":"v8.6.1","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>	2022-12-15 06:52:57 -07:00
Kibana Machine	7131e1baa6	[8.6] [Visualize2Lens] heatmap with dynamic bands is not converted correctly (#146970) (#146995) ... # Backport This will backport the following commits from `main` to `8.6`: - [[Visualize2Lens] heatmap with dynamic bands is not converted correctly (#146970)](https://github.com/elastic/kibana/pull/146970) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Uladzislau Lasitsa","email":"vlad.lasitsa@gmail.com"},"sourceCommit":{"committedDate":"2022-12-05T13:25:59Z","message":"[Visualize2Lens] heatmap with dynamic bands is not converted correctly (#146970)\n\n## Summary\r\n\r\nFixes: #146961\r\n\r\nFor dynamic calculated ranges in heatmap we should use percent palette.","sha":"131aa1b3c8fa0fc9dd8e1b31cb57dada65e7311b","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Heatmap","loe:hours","Team:Visualizations","release_note:skip","Feature:Lens","impact:medium","backport:prev-minor","v8.6.0","v8.7.0"],"number":146970,"url":"https://github.com/elastic/kibana/pull/146970","mergeCommit":{"message":"[Visualize2Lens] heatmap with dynamic bands is not converted correctly (#146970)\n\n## Summary\r\n\r\nFixes: #146961\r\n\r\nFor dynamic calculated ranges in heatmap we should use percent palette.","sha":"131aa1b3c8fa0fc9dd8e1b31cb57dada65e7311b"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/146970","number":146970,"mergeCommit":{"message":"[Visualize2Lens] heatmap with dynamic bands is not converted correctly (#146970)\n\n## Summary\r\n\r\nFixes: #146961\r\n\r\nFor dynamic calculated ranges in heatmap we should use percent palette.","sha":"131aa1b3c8fa0fc9dd8e1b31cb57dada65e7311b"}}]}] BACKPORT--> Co-authored-by: Uladzislau Lasitsa <vlad.lasitsa@gmail.com>	2022-12-05 07:32:18 -07:00
Kibana Machine	52a01cd472	[8.6] [ML] Automates geographic anomaly screenshots (#146502) (#146906) ... # Backport This will backport the following commits from `main` to `8.6`: - [[ML] Automates geographic anomaly screenshots (#146502)](https://github.com/elastic/kibana/pull/146502) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Lisa Cawley","email":"lcawley@elastic.co"},"sourceCommit":{"committedDate":"2022-12-02T17:20:09Z","message":"[ML] Automates geographic anomaly screenshots (#146502)\n\n\r\nCo-authored-by: Robert Oskamp <robert.oskamp@elastic.co>","sha":"e20ab5883b951ca621ebe04ff5fcb332d4a3e7c5","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":[":ml","release_note:skip","v8.7.0","v8.5.3","v8.6.1"],"number":146502,"url":"https://github.com/elastic/kibana/pull/146502","mergeCommit":{"message":"[ML] Automates geographic anomaly screenshots (#146502)\n\n\r\nCo-authored-by: Robert Oskamp <robert.oskamp@elastic.co>","sha":"e20ab5883b951ca621ebe04ff5fcb332d4a3e7c5"}},"sourceBranch":"main","suggestedTargetBranches":["8.5","8.6"],"targetPullRequestStates":[{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/146502","number":146502,"mergeCommit":{"message":"[ML] Automates geographic anomaly screenshots (#146502)\n\n\r\nCo-authored-by: Robert Oskamp <robert.oskamp@elastic.co>","sha":"e20ab5883b951ca621ebe04ff5fcb332d4a3e7c5"}},{"branch":"8.5","label":"v8.5.3","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.6","label":"v8.6.1","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Lisa Cawley <lcawley@elastic.co>	2022-12-02 11:13:39 -07:00
Kibana Machine	e7a9a25e7c	[8.6] [ML] Adds new screenshot to the generate anomaly alerts test suite (#146885) (#146895) ... # Backport This will backport the following commits from `main` to `8.6`: - [[ML] Adds new screenshot to the generate anomaly alerts test suite (#146885)](https://github.com/elastic/kibana/pull/146885) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"István Zoltán Szabó","email":"szabosteve@gmail.com"},"sourceCommit":{"committedDate":"2022-12-02T15:00:15Z","message":"[ML] Adds new screenshot to the generate anomaly alerts test suite (#146885)\n\n## Summary\r\n\r\nThis PR adds the necessary code to take the `ml-health-check-config`\r\nscreenshot in the generate anomaly alerts test suite.","sha":"8f076ffe73798b9f3ee6771f797948be354e9b6e","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":[":ml","release_note:skip","v8.6.0","v8.7.0","v8.5.3"],"number":146885,"url":"https://github.com/elastic/kibana/pull/146885","mergeCommit":{"message":"[ML] Adds new screenshot to the generate anomaly alerts test suite (#146885)\n\n## Summary\r\n\r\nThis PR adds the necessary code to take the `ml-health-check-config`\r\nscreenshot in the generate anomaly alerts test suite.","sha":"8f076ffe73798b9f3ee6771f797948be354e9b6e"}},"sourceBranch":"main","suggestedTargetBranches":["8.6","8.5"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/146885","number":146885,"mergeCommit":{"message":"[ML] Adds new screenshot to the generate anomaly alerts test suite (#146885)\n\n## Summary\r\n\r\nThis PR adds the necessary code to take the `ml-health-check-config`\r\nscreenshot in the generate anomaly alerts test suite.","sha":"8f076ffe73798b9f3ee6771f797948be354e9b6e"}},{"branch":"8.5","label":"v8.5.3","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: István Zoltán Szabó <szabosteve@gmail.com>	2022-12-02 08:52:46 -07:00
Kibana Machine	ed40c16ce9	[8.6] [ML] Adds anomaly alerts screenshot test suite (#146552) (#146861) ... # Backport This will backport the following commits from `main` to `8.6`: - [[ML] Adds anomaly alerts screenshot test suite (#146552)](https://github.com/elastic/kibana/pull/146552) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"István Zoltán Szabó","email":"szabosteve@gmail.com"},"sourceCommit":{"committedDate":"2022-12-02T10:01:51Z","message":"[ML] Adds anomaly alerts screenshot test suite (#146552)\n\n## Summary\r\n\r\nThis PR adds a new test suite to the screenshot creation script that\r\ncovers the screenshots on [Generating alerts for anomaly detection\r\njobs](https://www.elastic.co/guide/en/machine-learning/master/ml-configuring-alerts.html).","sha":"475e47ed993fba0ecd69caa211150f298e1eefe4","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":[":ml","release_note:skip","v8.6.0","v8.7.0","v8.5.3"],"number":146552,"url":"https://github.com/elastic/kibana/pull/146552","mergeCommit":{"message":"[ML] Adds anomaly alerts screenshot test suite (#146552)\n\n## Summary\r\n\r\nThis PR adds a new test suite to the screenshot creation script that\r\ncovers the screenshots on [Generating alerts for anomaly detection\r\njobs](https://www.elastic.co/guide/en/machine-learning/master/ml-configuring-alerts.html).","sha":"475e47ed993fba0ecd69caa211150f298e1eefe4"}},"sourceBranch":"main","suggestedTargetBranches":["8.6","8.5"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/146552","number":146552,"mergeCommit":{"message":"[ML] Adds anomaly alerts screenshot test suite (#146552)\n\n## Summary\r\n\r\nThis PR adds a new test suite to the screenshot creation script that\r\ncovers the screenshots on [Generating alerts for anomaly detection\r\njobs](https://www.elastic.co/guide/en/machine-learning/master/ml-configuring-alerts.html).","sha":"475e47ed993fba0ecd69caa211150f298e1eefe4"}},{"branch":"8.5","label":"v8.5.3","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: István Zoltán Szabó <szabosteve@gmail.com>	2022-12-02 04:10:06 -07:00
Kibana Machine	5351c0ab89	skip failing test suite (#146723)	2022-11-30 11:53:31 -05:00
Kibana Machine	36a6afacbc	[8.6] [ML] Functional tests for the Test Model action (#146399) (#146711) ... # Backport This will backport the following commits from `main` to `8.6`: - [[ML] Functional tests for the Test Model action (#146399)](https://github.com/elastic/kibana/pull/146399) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Dima Arnautov","email":"dmitrii.arnautov@elastic.co"},"sourceCommit":{"committedDate":"2022-11-30T15:48:27Z","message":"[ML] Functional tests for the Test Model action (#146399)\n\n## Summary\r\n\r\nPart of #142456\r\n\r\nAdds functional tests for the Test model action\r\n\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios","sha":"9ad78b244abb24eb0dc7f6c15ee511883a4d0ac1","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":[":ml","test_ui_functional","release_note:skip","Team:ML","v8.6.0","v8.7.0"],"number":146399,"url":"https://github.com/elastic/kibana/pull/146399","mergeCommit":{"message":"[ML] Functional tests for the Test Model action (#146399)\n\n## Summary\r\n\r\nPart of #142456\r\n\r\nAdds functional tests for the Test model action\r\n\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios","sha":"9ad78b244abb24eb0dc7f6c15ee511883a4d0ac1"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/146399","number":146399,"mergeCommit":{"message":"[ML] Functional tests for the Test Model action (#146399)\n\n## Summary\r\n\r\nPart of #142456\r\n\r\nAdds functional tests for the Test model action\r\n\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios","sha":"9ad78b244abb24eb0dc7f6c15ee511883a4d0ac1"}}]}] BACKPORT--> Co-authored-by: Dima Arnautov <dmitrii.arnautov@elastic.co>	2022-11-30 09:52:51 -07:00
Kibana Machine	e5e68c6c16	[8.6] Update Elastic Package Registry distribution docker image for V2 (#146673) (#146684) ... # Backport This will backport the following commits from `main` to `8.6`: - [Update Elastic Package Registry distribution docker image for V2 (#146673)](https://github.com/elastic/kibana/pull/146673) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Mario Rodriguez Molins","email":"mario.rodriguez@elastic.co"},"sourceCommit":{"committedDate":"2022-11-30T13:19:32Z","message":"Update Elastic Package Registry distribution docker image for V2 (#146673)\n\n## Summary\r\n\r\nUpdate the docker image used as Elastic Package Registry distribution\r\nfor Package Storage V2, so it contains the latest packages published.\r\n\r\nTested updating fleet_packages.json to use endpoint version 8.6.0 (and\r\nreverted).","sha":"c6c612ef81ed7c11d3b0a39ea6d3579e7bd6cabe","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Fleet","backport:prev-minor","v8.7.0"],"number":146673,"url":"https://github.com/elastic/kibana/pull/146673","mergeCommit":{"message":"Update Elastic Package Registry distribution docker image for V2 (#146673)\n\n## Summary\r\n\r\nUpdate the docker image used as Elastic Package Registry distribution\r\nfor Package Storage V2, so it contains the latest packages published.\r\n\r\nTested updating fleet_packages.json to use endpoint version 8.6.0 (and\r\nreverted).","sha":"c6c612ef81ed7c11d3b0a39ea6d3579e7bd6cabe"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/146673","number":146673,"mergeCommit":{"message":"Update Elastic Package Registry distribution docker image for V2 (#146673)\n\n## Summary\r\n\r\nUpdate the docker image used as Elastic Package Registry distribution\r\nfor Package Storage V2, so it contains the latest packages published.\r\n\r\nTested updating fleet_packages.json to use endpoint version 8.6.0 (and\r\nreverted).","sha":"c6c612ef81ed7c11d3b0a39ea6d3579e7bd6cabe"}}]}] BACKPORT--> Co-authored-by: Mario Rodriguez Molins <mario.rodriguez@elastic.co>	2022-11-30 07:30:20 -07:00
Kibana Machine	1b2ce1a5a8	[8.6] Fixes issue in sorting using TX and RX columns (#145994) (#146509) ... # Backport This will backport the following commits from `main` to `8.6`: - [Fixes issue in sorting using TX and RX columns (#145994)](https://github.com/elastic/kibana/pull/145994) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"mohamedhamed-ahmed","email":"eng_mohamedhamed@hotmail.com"},"sourceCommit":{"committedDate":"2022-11-29T09:41:18Z","message":"Fixes issue in sorting using TX and RX columns (#145994)\n\n## Summary\r\ncloses #142667\r\nMore details about the issue can be found\r\n[here](https://github.com/elastic/kibana/issues/142667)\r\n\r\n## Problem \r\n\r\nThe problem here is the use of bucket script in the query which doesn't\r\nreturn a single metric value and thus can't be used for pipeline\r\naggregation.\r\n```\r\nbucket_script: {\r\n buckets_path: {\r\n value: 'rx_avg',\r\n period: 'rx_period>period',\r\n },\r\n script: {\r\n source: 'params.value / (params.period / 1000)',\r\n lang: 'painless',\r\n },\r\n gap_policy: 'skip'\r\n }\r\n```\r\n\r\n## Proposed Solutions:\r\n\r\n1. Using\r\n[Runtime](https://www.elastic.co/guide/en/elasticsearch/reference/current/runtime.html)\r\nfield as below:\r\n```\r\n\"runtime_mappings\": {\r\n \"rx_bytes_per_period\": {\r\n \"type\": \"long\",\r\n \"script\": {\r\n \"source\": \"\"\"\r\n emit(doc['host.network.ingress.bytes'].size()==0 ? -1 : (doc['host.network.ingress.bytes'].value/doc['metricset.period'].value));\r\n \"\"\"\r\n }\r\n }\r\n }\r\n```\r\n\r\n2. Using\r\n[Scripted_Metric](https://www.elastic.co/guide/en/elasticsearch/reference/current/search-aggregations-metrics-scripted-metric-aggregation.html):\r\n\r\n```\r\nscripted_metric\": {\r\n \"init_script\": \"state.bytes_per_period = []\",\r\n \"map_script\": \"state.bytes_per_period.add(doc['host.network.ingress.bytes'].value/(doc['metricset.period'].value/1000))\",\r\n \"combine_script\": \"double avg_bytes_per_period = 0; for (t in state.bytes_per_period) { avg_bytes_per_period += t } return avg_bytes_per_period/state.bytes_per_period.size()\",\r\n \"reduce_script\": \"double result = 0; for (a in states) { result += a) } return result/states.size()\"\r\n }\r\n```\r\n\r\n## Conclusion\r\n\r\nI decided to go with the runtime field as its a bit more concise and\r\neasier to understand and performance wise it was slightly faster than\r\nthe scripted metric in most times.\r\n\r\n### Testing\r\n\r\nNavigate to `Observability` -> `Overview` -> `Hosts Table` try to filter\r\nwith Rx and Tx columns","sha":"6e4f22d12dfc18ceff35b9bd0f6038b7fbf5ec7b","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Infra Monitoring UI","Feature:Observability Overview","backport:prev-minor","v8.7.0"],"number":145994,"url":"https://github.com/elastic/kibana/pull/145994","mergeCommit":{"message":"Fixes issue in sorting using TX and RX columns (#145994)\n\n## Summary\r\ncloses #142667\r\nMore details about the issue can be found\r\n[here](https://github.com/elastic/kibana/issues/142667)\r\n\r\n## Problem \r\n\r\nThe problem here is the use of bucket script in the query which doesn't\r\nreturn a single metric value and thus can't be used for pipeline\r\naggregation.\r\n```\r\nbucket_script: {\r\n buckets_path: {\r\n value: 'rx_avg',\r\n period: 'rx_period>period',\r\n },\r\n script: {\r\n source: 'params.value / (params.period / 1000)',\r\n lang: 'painless',\r\n },\r\n gap_policy: 'skip'\r\n }\r\n```\r\n\r\n## Proposed Solutions:\r\n\r\n1. Using\r\n[Runtime](https://www.elastic.co/guide/en/elasticsearch/reference/current/runtime.html)\r\nfield as below:\r\n```\r\n\"runtime_mappings\": {\r\n \"rx_bytes_per_period\": {\r\n \"type\": \"long\",\r\n \"script\": {\r\n \"source\": \"\"\"\r\n emit(doc['host.network.ingress.bytes'].size()==0 ? -1 : (doc['host.network.ingress.bytes'].value/doc['metricset.period'].value));\r\n \"\"\"\r\n }\r\n }\r\n }\r\n```\r\n\r\n2. Using\r\n[Scripted_Metric](https://www.elastic.co/guide/en/elasticsearch/reference/current/search-aggregations-metrics-scripted-metric-aggregation.html):\r\n\r\n```\r\nscripted_metric\": {\r\n \"init_script\": \"state.bytes_per_period = []\",\r\n \"map_script\": \"state.bytes_per_period.add(doc['host.network.ingress.bytes'].value/(doc['metricset.period'].value/1000))\",\r\n \"combine_script\": \"double avg_bytes_per_period = 0; for (t in state.bytes_per_period) { avg_bytes_per_period += t } return avg_bytes_per_period/state.bytes_per_period.size()\",\r\n \"reduce_script\": \"double result = 0; for (a in states) { result += a) } return result/states.size()\"\r\n }\r\n```\r\n\r\n## Conclusion\r\n\r\nI decided to go with the runtime field as its a bit more concise and\r\neasier to understand and performance wise it was slightly faster than\r\nthe scripted metric in most times.\r\n\r\n### Testing\r\n\r\nNavigate to `Observability` -> `Overview` -> `Hosts Table` try to filter\r\nwith Rx and Tx columns","sha":"6e4f22d12dfc18ceff35b9bd0f6038b7fbf5ec7b"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/145994","number":145994,"mergeCommit":{"message":"Fixes issue in sorting using TX and RX columns (#145994)\n\n## Summary\r\ncloses #142667\r\nMore details about the issue can be found\r\n[here](https://github.com/elastic/kibana/issues/142667)\r\n\r\n## Problem \r\n\r\nThe problem here is the use of bucket script in the query which doesn't\r\nreturn a single metric value and thus can't be used for pipeline\r\naggregation.\r\n```\r\nbucket_script: {\r\n buckets_path: {\r\n value: 'rx_avg',\r\n period: 'rx_period>period',\r\n },\r\n script: {\r\n source: 'params.value / (params.period / 1000)',\r\n lang: 'painless',\r\n },\r\n gap_policy: 'skip'\r\n }\r\n```\r\n\r\n## Proposed Solutions:\r\n\r\n1. Using\r\n[Runtime](https://www.elastic.co/guide/en/elasticsearch/reference/current/runtime.html)\r\nfield as below:\r\n```\r\n\"runtime_mappings\": {\r\n \"rx_bytes_per_period\": {\r\n \"type\": \"long\",\r\n \"script\": {\r\n \"source\": \"\"\"\r\n emit(doc['host.network.ingress.bytes'].size()==0 ? -1 : (doc['host.network.ingress.bytes'].value/doc['metricset.period'].value));\r\n \"\"\"\r\n }\r\n }\r\n }\r\n```\r\n\r\n2. Using\r\n[Scripted_Metric](https://www.elastic.co/guide/en/elasticsearch/reference/current/search-aggregations-metrics-scripted-metric-aggregation.html):\r\n\r\n```\r\nscripted_metric\": {\r\n \"init_script\": \"state.bytes_per_period = []\",\r\n \"map_script\": \"state.bytes_per_period.add(doc['host.network.ingress.bytes'].value/(doc['metricset.period'].value/1000))\",\r\n \"combine_script\": \"double avg_bytes_per_period = 0; for (t in state.bytes_per_period) { avg_bytes_per_period += t } return avg_bytes_per_period/state.bytes_per_period.size()\",\r\n \"reduce_script\": \"double result = 0; for (a in states) { result += a) } return result/states.size()\"\r\n }\r\n```\r\n\r\n## Conclusion\r\n\r\nI decided to go with the runtime field as its a bit more concise and\r\neasier to understand and performance wise it was slightly faster than\r\nthe scripted metric in most times.\r\n\r\n### Testing\r\n\r\nNavigate to `Observability` -> `Overview` -> `Hosts Table` try to filter\r\nwith Rx and Tx columns","sha":"6e4f22d12dfc18ceff35b9bd0f6038b7fbf5ec7b"}}]}] BACKPORT--> Co-authored-by: mohamedhamed-ahmed <eng_mohamedhamed@hotmail.com>	2022-11-29 03:47:22 -07:00
Kibana Machine	d00d67ddd0	[8.6] fix for the skipped functional test sync_colors.ts (#146083) (#146457) ... # Backport This will backport the following commits from `main` to `8.6`: - [fix for the skipped functional test `sync_colors.ts` (#146083)](https://github.com/elastic/kibana/pull/146083) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Rashmi Kulkarni","email":"rashmi.kulkarni@elastic.co"},"sourceCommit":{"committedDate":"2022-11-28T18:08:50Z","message":"fix for the skipped functional test `sync_colors.ts` (#146083)\n\ntrying to fix https://github.com/elastic/kibana/issues/97403\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"a270d75f36207567f340a63b3666f9229deb7a7f","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Presentation","release_note:skip","v8.6.0","v8.7.0"],"number":146083,"url":"https://github.com/elastic/kibana/pull/146083","mergeCommit":{"message":"fix for the skipped functional test `sync_colors.ts` (#146083)\n\ntrying to fix https://github.com/elastic/kibana/issues/97403\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"a270d75f36207567f340a63b3666f9229deb7a7f"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/146083","number":146083,"mergeCommit":{"message":"fix for the skipped functional test `sync_colors.ts` (#146083)\n\ntrying to fix https://github.com/elastic/kibana/issues/97403\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"a270d75f36207567f340a63b3666f9229deb7a7f"}}]}] BACKPORT--> Co-authored-by: Rashmi Kulkarni <rashmi.kulkarni@elastic.co>	2022-11-28 12:13:59 -07:00
Kibana Machine	82bf59b272	[8.6] [UA] fix flaky test (#146351) (#146441) ... # Backport This will backport the following commits from `main` to `8.6`: - [[UA] fix flaky test (#146351)](https://github.com/elastic/kibana/pull/146351) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Ahmad Bamieh","email":"ahmad.bamyeh@elastic.co"},"sourceCommit":{"committedDate":"2022-11-28T16:52:15Z","message":"[UA] fix flaky test (#146351)\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCloses https://github.com/elastic/kibana/issues/144885","sha":"ab8dd04073a4f9b8bcf26444f35a33d85f98b600","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v8.6.0","v8.7.0","8.6.1"],"number":146351,"url":"https://github.com/elastic/kibana/pull/146351","mergeCommit":{"message":"[UA] fix flaky test (#146351)\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCloses https://github.com/elastic/kibana/issues/144885","sha":"ab8dd04073a4f9b8bcf26444f35a33d85f98b600"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/146351","number":146351,"mergeCommit":{"message":"[UA] fix flaky test (#146351)\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCloses https://github.com/elastic/kibana/issues/144885","sha":"ab8dd04073a4f9b8bcf26444f35a33d85f98b600"}}]}] BACKPORT--> Co-authored-by: Ahmad Bamieh <ahmad.bamyeh@elastic.co>	2022-11-28 10:56:36 -07:00
Kibana Machine	e6c75cd1cd	[8.6] fix timepicker default start day (#145947) (#146408) ... # Backport This will backport the following commits from `main` to `8.6`: - [fix timepicker default start day (#145947)](https://github.com/elastic/kibana/pull/145947) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Lee Drengenberg","email":"lee.drengenberg@elastic.co"},"sourceCommit":{"committedDate":"2022-11-28T14:59:09Z","message":"fix timepicker default start day (#145947)\n\n## Summary\r\n\r\nThis PR is mainly some cleanup before another PR I have in the works to\r\nshortcut timepicker.setAbsoluteTime() by checking if we already have the\r\ndesired time set.\r\n\r\nThis PR changes the timePicker defaultStartTimeUTC value from September\r\n18th to September 19th to match the value of defaultStartTimeUTC.\r\nThe variable name defaultStartTimeUTC implies it's a different timezone\r\nbut actually it's the same date time but in a different ISO format.\r\nIt seems there was only 1 place in tests which expected that Sep 18th\r\ndate.\r\n\r\nAnother small change in\r\n`x-pack/test/functional/apps/lens/group1/text_based_languages.ts` is to\r\nuse uiSettings.update insteda of uiSettings.replace. `replace` wipes out\r\nthe default UTC timezone and the defaultTime settings.\r\n\r\nI added a few calls to cleanStandardList to make sure any saved objects\r\ncreated by the tests are cleaned up, and to get a clean run if other\r\ntests left something.\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"9c9c66cd0b16f7514b407912d1b0bbcb0cab00ac","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:QA","test_ui_functional","release_note:skip","backport:prev-minor","v8.7.0"],"number":145947,"url":"https://github.com/elastic/kibana/pull/145947","mergeCommit":{"message":"fix timepicker default start day (#145947)\n\n## Summary\r\n\r\nThis PR is mainly some cleanup before another PR I have in the works to\r\nshortcut timepicker.setAbsoluteTime() by checking if we already have the\r\ndesired time set.\r\n\r\nThis PR changes the timePicker defaultStartTimeUTC value from September\r\n18th to September 19th to match the value of defaultStartTimeUTC.\r\nThe variable name defaultStartTimeUTC implies it's a different timezone\r\nbut actually it's the same date time but in a different ISO format.\r\nIt seems there was only 1 place in tests which expected that Sep 18th\r\ndate.\r\n\r\nAnother small change in\r\n`x-pack/test/functional/apps/lens/group1/text_based_languages.ts` is to\r\nuse uiSettings.update insteda of uiSettings.replace. `replace` wipes out\r\nthe default UTC timezone and the defaultTime settings.\r\n\r\nI added a few calls to cleanStandardList to make sure any saved objects\r\ncreated by the tests are cleaned up, and to get a clean run if other\r\ntests left something.\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"9c9c66cd0b16f7514b407912d1b0bbcb0cab00ac"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/145947","number":145947,"mergeCommit":{"message":"fix timepicker default start day (#145947)\n\n## Summary\r\n\r\nThis PR is mainly some cleanup before another PR I have in the works to\r\nshortcut timepicker.setAbsoluteTime() by checking if we already have the\r\ndesired time set.\r\n\r\nThis PR changes the timePicker defaultStartTimeUTC value from September\r\n18th to September 19th to match the value of defaultStartTimeUTC.\r\nThe variable name defaultStartTimeUTC implies it's a different timezone\r\nbut actually it's the same date time but in a different ISO format.\r\nIt seems there was only 1 place in tests which expected that Sep 18th\r\ndate.\r\n\r\nAnother small change in\r\n`x-pack/test/functional/apps/lens/group1/text_based_languages.ts` is to\r\nuse uiSettings.update insteda of uiSettings.replace. `replace` wipes out\r\nthe default UTC timezone and the defaultTime settings.\r\n\r\nI added a few calls to cleanStandardList to make sure any saved objects\r\ncreated by the tests are cleaned up, and to get a clean run if other\r\ntests left something.\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"9c9c66cd0b16f7514b407912d1b0bbcb0cab00ac"}}]}] BACKPORT--> Co-authored-by: Lee Drengenberg <lee.drengenberg@elastic.co>	2022-11-28 09:25:22 -07:00
Kibana Machine	b7d1fd7cda	[8.6] [ML] Functional tests - stabilize index data visualizer tests (#146285) (#146307) ... # Backport This will backport the following commits from `main` to `8.6`: - [[ML] Functional tests - stabilize index data visualizer tests (#146285)](https://github.com/elastic/kibana/pull/146285) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Robert Oskamp","email":"robert.oskamp@elastic.co"},"sourceCommit":{"committedDate":"2022-11-24T15:41:43Z","message":"[ML] Functional tests - stabilize index data visualizer tests (#146285)\n\nThis PR stabilizes the index data visualizer tests.","sha":"40a424b5ea5b0e36b9a74830355e9cfc30964f7e","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":[":ml","test_ui_functional","release_note:skip","backport:prev-minor","v8.6.0","v8.7.0"],"number":146285,"url":"https://github.com/elastic/kibana/pull/146285","mergeCommit":{"message":"[ML] Functional tests - stabilize index data visualizer tests (#146285)\n\nThis PR stabilizes the index data visualizer tests.","sha":"40a424b5ea5b0e36b9a74830355e9cfc30964f7e"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/146285","number":146285,"mergeCommit":{"message":"[ML] Functional tests - stabilize index data visualizer tests (#146285)\n\nThis PR stabilizes the index data visualizer tests.","sha":"40a424b5ea5b0e36b9a74830355e9cfc30964f7e"}}]}] BACKPORT--> Co-authored-by: Robert Oskamp <robert.oskamp@elastic.co>	2022-11-24 10:04:55 -07:00
Kibana Machine	ab4cecc503	[8.6] [ML] Functional tests - stabilize notifications tests (#146280) (#146294) ... # Backport This will backport the following commits from `main` to `8.6`: - [[ML] Functional tests - stabilize notifications tests (#146280)](https://github.com/elastic/kibana/pull/146280) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Robert Oskamp","email":"robert.oskamp@elastic.co"},"sourceCommit":{"committedDate":"2022-11-24T14:16:34Z","message":"[ML] Functional tests - stabilize notifications tests (#146280)\n\nThis PR stabilizes the functional UI tests for the ML notifications page.","sha":"820cffddb9067dc820e2c0c98ca50466bcdf1f28","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":[":ml","test_ui_functional","release_note:skip","backport:prev-minor","v8.6.0","v8.7.0"],"number":146280,"url":"https://github.com/elastic/kibana/pull/146280","mergeCommit":{"message":"[ML] Functional tests - stabilize notifications tests (#146280)\n\nThis PR stabilizes the functional UI tests for the ML notifications page.","sha":"820cffddb9067dc820e2c0c98ca50466bcdf1f28"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/146280","number":146280,"mergeCommit":{"message":"[ML] Functional tests - stabilize notifications tests (#146280)\n\nThis PR stabilizes the functional UI tests for the ML notifications page.","sha":"820cffddb9067dc820e2c0c98ca50466bcdf1f28"}}]}] BACKPORT--> Co-authored-by: Robert Oskamp <robert.oskamp@elastic.co>	2022-11-24 08:12:02 -07:00
Kibana Machine	d9f0ccc247	[8.6] [ML] Explain Log Rate Spikes: Additional API integration tests (#146113) (#146263) ... # Backport This will backport the following commits from `main` to `8.6`: - [[ML] Explain Log Rate Spikes: Additional API integration tests (#146113)](https://github.com/elastic/kibana/pull/146113) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Walter Rafelsberger","email":"walter.rafelsberger@elastic.co"},"sourceCommit":{"committedDate":"2022-11-24T09:41:11Z","message":"[ML] Explain Log Rate Spikes: Additional API integration tests (#146113)\n\nAdditional API integration tests.\r\n\r\n- The test data was moved to its own file `test_data.ts` and types for\r\nits structure defined in `types.ts` to be in line with the structure\r\nused for functional tests.\r\n- The file that runs the test was extended so it can run an array of\r\ntest data definitions.\r\n- The datasets used in the funcional tests (`ecommerce` with some\r\nadditional documents added to create a significant spike and the\r\ncomputationally generated spike data set to create distinct groups) were\r\nmoved to a service `ExplainLogRateSpikesDataGenerator` so they can be\r\ngenerated and used across functional and API integration tests.\r\n- The computationally generated spike data set\r\n`artificial_logs_with_spike` is now also used for API integration tests.\r\n- Additional assertions have been added to check the grouping result.\r\n`ecommerce` does not return any groups whereas\r\n`artificial_logs_with_spike` does.\r\n- The functional tests code is now consolidated and one test file is\r\nable to run multiple test data definitions too.","sha":"5481f07f79e6923a982ae5ce42af051630b10646","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":[":ml","release_note:skip","Feature:ML/AIOps","v8.6.0","v8.7.0"],"number":146113,"url":"https://github.com/elastic/kibana/pull/146113","mergeCommit":{"message":"[ML] Explain Log Rate Spikes: Additional API integration tests (#146113)\n\nAdditional API integration tests.\r\n\r\n- The test data was moved to its own file `test_data.ts` and types for\r\nits structure defined in `types.ts` to be in line with the structure\r\nused for functional tests.\r\n- The file that runs the test was extended so it can run an array of\r\ntest data definitions.\r\n- The datasets used in the funcional tests (`ecommerce` with some\r\nadditional documents added to create a significant spike and the\r\ncomputationally generated spike data set to create distinct groups) were\r\nmoved to a service `ExplainLogRateSpikesDataGenerator` so they can be\r\ngenerated and used across functional and API integration tests.\r\n- The computationally generated spike data set\r\n`artificial_logs_with_spike` is now also used for API integration tests.\r\n- Additional assertions have been added to check the grouping result.\r\n`ecommerce` does not return any groups whereas\r\n`artificial_logs_with_spike` does.\r\n- The functional tests code is now consolidated and one test file is\r\nable to run multiple test data definitions too.","sha":"5481f07f79e6923a982ae5ce42af051630b10646"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/146113","number":146113,"mergeCommit":{"message":"[ML] Explain Log Rate Spikes: Additional API integration tests (#146113)\n\nAdditional API integration tests.\r\n\r\n- The test data was moved to its own file `test_data.ts` and types for\r\nits structure defined in `types.ts` to be in line with the structure\r\nused for functional tests.\r\n- The file that runs the test was extended so it can run an array of\r\ntest data definitions.\r\n- The datasets used in the funcional tests (`ecommerce` with some\r\nadditional documents added to create a significant spike and the\r\ncomputationally generated spike data set to create distinct groups) were\r\nmoved to a service `ExplainLogRateSpikesDataGenerator` so they can be\r\ngenerated and used across functional and API integration tests.\r\n- The computationally generated spike data set\r\n`artificial_logs_with_spike` is now also used for API integration tests.\r\n- Additional assertions have been added to check the grouping result.\r\n`ecommerce` does not return any groups whereas\r\n`artificial_logs_with_spike` does.\r\n- The functional tests code is now consolidated and one test file is\r\nable to run multiple test data definitions too.","sha":"5481f07f79e6923a982ae5ce42af051630b10646"}}]}] BACKPORT--> Co-authored-by: Walter Rafelsberger <walter.rafelsberger@elastic.co>	2022-11-24 04:09:20 -07:00
Kibana Machine	c929f357fa	[8.6] [ML] Anomaly Detection: Adds functional tests for filtering by influencers in the Anomaly Explorer (#146085) (#146215) ... # Backport This will backport the following commits from `main` to `8.6`: - [[ML] Anomaly Detection: Adds functional tests for filtering by influencers in the Anomaly Explorer (#146085)](https://github.com/elastic/kibana/pull/146085) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Melissa Alvarez","email":"melissa.alvarez@elastic.co"},"sourceCommit":{"committedDate":"2022-11-23T19:00:34Z","message":"[ML] Anomaly Detection: Adds functional tests for filtering by influencers in the Anomaly Explorer (#146085)\n\n## Summary\r\n\r\nRelated meta issue: https://github.com/elastic/kibana/issues/142456\r\nAdds functional tests for filtering by influencers in the Anomaly\r\nExplorer\r\n\r\nFlaky test build\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/1592\r\n\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [x ] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"395fe5a0919d190cd8333af96c787efc36e4a389","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":[":ml","test_ui_functional","release_note:skip","v8.6.0","v8.7.0"],"number":146085,"url":"https://github.com/elastic/kibana/pull/146085","mergeCommit":{"message":"[ML] Anomaly Detection: Adds functional tests for filtering by influencers in the Anomaly Explorer (#146085)\n\n## Summary\r\n\r\nRelated meta issue: https://github.com/elastic/kibana/issues/142456\r\nAdds functional tests for filtering by influencers in the Anomaly\r\nExplorer\r\n\r\nFlaky test build\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/1592\r\n\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [x ] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"395fe5a0919d190cd8333af96c787efc36e4a389"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/146085","number":146085,"mergeCommit":{"message":"[ML] Anomaly Detection: Adds functional tests for filtering by influencers in the Anomaly Explorer (#146085)\n\n## Summary\r\n\r\nRelated meta issue: https://github.com/elastic/kibana/issues/142456\r\nAdds functional tests for filtering by influencers in the Anomaly\r\nExplorer\r\n\r\nFlaky test build\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/1592\r\n\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [x ] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"395fe5a0919d190cd8333af96c787efc36e4a389"}}]}] BACKPORT--> Co-authored-by: Melissa Alvarez <melissa.alvarez@elastic.co>	2022-11-23 13:06:26 -07:00
Kibana Machine	010bb24b87	[8.6] [ML] Explain Log Rate Spikes: Additional functional tests with artificial logs dataset (#145763) (#146038) ... # Backport This will backport the following commits from `main` to `8.6`: - [[ML] Explain Log Rate Spikes: Additional functional tests with artificial logs dataset (#145763)](https://github.com/elastic/kibana/pull/145763) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Walter Rafelsberger","email":"walter.rafelsberger@elastic.co"},"sourceCommit":{"committedDate":"2022-11-22T17:28:54Z","message":"[ML] Explain Log Rate Spikes: Additional functional tests with artificial logs dataset (#145763)\n\nAdditional functional tests with artificial logs dataset.\r\n\r\nThis generates an artificial logs dataset with the purpose of asserting\r\nthe case where grouping needs to identify 2 non-overlapping groups. The\r\nprimary use case of the test is to track possible regressions related to\r\nwhen trying to improve `frequent_items` aggregation settings and the\r\ncustom grouping code.","sha":"c45f55660584381d385e11817d4285e3e24eb546","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":[":ml","release_note:skip","Feature:ML/AIOps","v8.6.0","v8.7.0"],"number":145763,"url":"https://github.com/elastic/kibana/pull/145763","mergeCommit":{"message":"[ML] Explain Log Rate Spikes: Additional functional tests with artificial logs dataset (#145763)\n\nAdditional functional tests with artificial logs dataset.\r\n\r\nThis generates an artificial logs dataset with the purpose of asserting\r\nthe case where grouping needs to identify 2 non-overlapping groups. The\r\nprimary use case of the test is to track possible regressions related to\r\nwhen trying to improve `frequent_items` aggregation settings and the\r\ncustom grouping code.","sha":"c45f55660584381d385e11817d4285e3e24eb546"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/145763","number":145763,"mergeCommit":{"message":"[ML] Explain Log Rate Spikes: Additional functional tests with artificial logs dataset (#145763)\n\nAdditional functional tests with artificial logs dataset.\r\n\r\nThis generates an artificial logs dataset with the purpose of asserting\r\nthe case where grouping needs to identify 2 non-overlapping groups. The\r\nprimary use case of the test is to track possible regressions related to\r\nwhen trying to improve `frequent_items` aggregation settings and the\r\ncustom grouping code.","sha":"c45f55660584381d385e11817d4285e3e24eb546"}}]}] BACKPORT--> Co-authored-by: Walter Rafelsberger <walter.rafelsberger@elastic.co>	2022-11-22 12:01:26 -07:00
Kibana Machine	cc1a155cd6	[8.6] Adjust CCS Remote Clusters Test To Find Index Based On Index Name (#145786) (#146043) ... # Backport This will backport the following commits from `main` to `8.6`: - [Adjust CCS Remote Clusters Test To Find Index Based On Index Name (#145786)](https://github.com/elastic/kibana/pull/145786) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"John Dorlus","email":"jsdorlus@elastic.co"},"sourceCommit":{"committedDate":"2022-11-22T16:55:14Z","message":"Adjust CCS Remote Clusters Test To Find Index Based On Index Name (#145786)","sha":"8e1618ac905d33de2963c23a2296204f8e60d44a","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:QA","test_ui_functional","test_xpack_functional","release_note:skip","Feature:Functional Testing","backport:prev-minor","v8.7.0"],"number":145786,"url":"https://github.com/elastic/kibana/pull/145786","mergeCommit":{"message":"Adjust CCS Remote Clusters Test To Find Index Based On Index Name (#145786)","sha":"8e1618ac905d33de2963c23a2296204f8e60d44a"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/145786","number":145786,"mergeCommit":{"message":"Adjust CCS Remote Clusters Test To Find Index Based On Index Name (#145786)","sha":"8e1618ac905d33de2963c23a2296204f8e60d44a"}}]}] BACKPORT--> Co-authored-by: John Dorlus <jsdorlus@elastic.co>	2022-11-22 11:46:42 -07:00
Kibana Machine	52133e6c41	[8.6] [Stack Monitoring] api tests for cluster and elasticsearch (#145138) (#145985) ... # Backport This will backport the following commits from `main` to `8.6`: - [[Stack Monitoring] api tests for cluster and elasticsearch (#145138)](https://github.com/elastic/kibana/pull/145138) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Kevin Lacabane","email":"kevin.lacabane@elastic.co"},"sourceCommit":{"committedDate":"2022-11-22T13:02:50Z","message":"[Stack Monitoring] api tests for cluster and elasticsearch (#145138)\n\n### Summary\r\nPart of https://github.com/elastic/kibana/issues/119658\r\n\r\nAdd api integration tests for cluster and elasticsearch routes to\r\nvalidate behavior when reading data ingested by elastic-agent.\r\n\r\nWe currently have a testing suite for legacy and another one for\r\nmetricbeat. Since metricbeat and agent documents only differ in their\r\nmetadata, for example agent will populate a `data_stream.*` property to\r\nidentify the document types while metricbeat uses `metricset.*`, the\r\ntests assertion validating _business_ data should pass regardless of the\r\ndocuments source. With this in mind the metricbeat tests were updated to\r\nrun the tests twice, one time with metricbeat data and a second time\r\nwith package data.\r\n\r\nTo generate the archives the `metrics-*` mappings were extracted with\r\nesArchiver from an elasticsearch with the package installed, and the\r\ndocuments were transformed from the metricbeat documents with [this\r\nscript](https://gist.github.com/klacabane/654497ff86053c60af6df15fa6f6f657).\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"5cf0d0f24817db4b36501c6c06f6cfb4cd61c296","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Infra Monitoring UI","release_note:skip","Feature:Stack Monitoring","v8.6.0","v8.7.0"],"number":145138,"url":"https://github.com/elastic/kibana/pull/145138","mergeCommit":{"message":"[Stack Monitoring] api tests for cluster and elasticsearch (#145138)\n\n### Summary\r\nPart of https://github.com/elastic/kibana/issues/119658\r\n\r\nAdd api integration tests for cluster and elasticsearch routes to\r\nvalidate behavior when reading data ingested by elastic-agent.\r\n\r\nWe currently have a testing suite for legacy and another one for\r\nmetricbeat. Since metricbeat and agent documents only differ in their\r\nmetadata, for example agent will populate a `data_stream.*` property to\r\nidentify the document types while metricbeat uses `metricset.*`, the\r\ntests assertion validating _business_ data should pass regardless of the\r\ndocuments source. With this in mind the metricbeat tests were updated to\r\nrun the tests twice, one time with metricbeat data and a second time\r\nwith package data.\r\n\r\nTo generate the archives the `metrics-*` mappings were extracted with\r\nesArchiver from an elasticsearch with the package installed, and the\r\ndocuments were transformed from the metricbeat documents with [this\r\nscript](https://gist.github.com/klacabane/654497ff86053c60af6df15fa6f6f657).\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"5cf0d0f24817db4b36501c6c06f6cfb4cd61c296"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/145138","number":145138,"mergeCommit":{"message":"[Stack Monitoring] api tests for cluster and elasticsearch (#145138)\n\n### Summary\r\nPart of https://github.com/elastic/kibana/issues/119658\r\n\r\nAdd api integration tests for cluster and elasticsearch routes to\r\nvalidate behavior when reading data ingested by elastic-agent.\r\n\r\nWe currently have a testing suite for legacy and another one for\r\nmetricbeat. Since metricbeat and agent documents only differ in their\r\nmetadata, for example agent will populate a `data_stream.*` property to\r\nidentify the document types while metricbeat uses `metricset.*`, the\r\ntests assertion validating _business_ data should pass regardless of the\r\ndocuments source. With this in mind the metricbeat tests were updated to\r\nrun the tests twice, one time with metricbeat data and a second time\r\nwith package data.\r\n\r\nTo generate the archives the `metrics-*` mappings were extracted with\r\nesArchiver from an elasticsearch with the package installed, and the\r\ndocuments were transformed from the metricbeat documents with [this\r\nscript](https://gist.github.com/klacabane/654497ff86053c60af6df15fa6f6f657).\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"5cf0d0f24817db4b36501c6c06f6cfb4cd61c296"}}]}] BACKPORT--> Co-authored-by: Kevin Lacabane <kevin.lacabane@elastic.co>	2022-11-22 07:10:57 -07:00
Kibana Machine	50e50f0737	[8.6] unload from remote (#145641) (#145914) ... # Backport This will backport the following commits from `main` to `8.6`: - [unload from remote (#145641)](https://github.com/elastic/kibana/pull/145641) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Lee Drengenberg","email":"lee.drengenberg@elastic.co"},"sourceCommit":{"committedDate":"2022-11-21T18:39:39Z","message":"unload from remote (#145641)\n\n## Summary\r\n\r\nIt appears that the before method sets esNode to either esArchiver or\r\nremoteEsArchiver, but in the after method it uses esArchiver. This\r\ncauses the unload to fail on the CCS case.","sha":"393b37811dbaa46a4a1ca6fa22d8941e580854c4","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:QA","release_note:skip","backport:prev-minor","v8.7.0"],"number":145641,"url":"https://github.com/elastic/kibana/pull/145641","mergeCommit":{"message":"unload from remote (#145641)\n\n## Summary\r\n\r\nIt appears that the before method sets esNode to either esArchiver or\r\nremoteEsArchiver, but in the after method it uses esArchiver. This\r\ncauses the unload to fail on the CCS case.","sha":"393b37811dbaa46a4a1ca6fa22d8941e580854c4"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/145641","number":145641,"mergeCommit":{"message":"unload from remote (#145641)\n\n## Summary\r\n\r\nIt appears that the before method sets esNode to either esArchiver or\r\nremoteEsArchiver, but in the after method it uses esArchiver. This\r\ncauses the unload to fail on the CCS case.","sha":"393b37811dbaa46a4a1ca6fa22d8941e580854c4"}}]}] BACKPORT--> Co-authored-by: Lee Drengenberg <lee.drengenberg@elastic.co>	2022-11-21 12:44:16 -07:00
Kibana Machine	d6fb3e08da	[8.6] [ML] Fix a redirect loop (#145738) (#145904) ... # Backport This will backport the following commits from `main` to `8.6`: - [[ML] Fix a redirect loop (#145738)](https://github.com/elastic/kibana/pull/145738) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Dima Arnautov","email":"dmitrii.arnautov@elastic.co"},"sourceCommit":{"committedDate":"2022-11-21T17:56:33Z","message":"[ML] Fix a redirect loop (#145738)","sha":"4d1495440842106f389dd85c81eb2cda1617d099","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix",":ml","Team:ML","v8.6.0","v8.7.0"],"number":145738,"url":"https://github.com/elastic/kibana/pull/145738","mergeCommit":{"message":"[ML] Fix a redirect loop (#145738)","sha":"4d1495440842106f389dd85c81eb2cda1617d099"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/145738","number":145738,"mergeCommit":{"message":"[ML] Fix a redirect loop (#145738)","sha":"4d1495440842106f389dd85c81eb2cda1617d099"}}]}] BACKPORT--> Co-authored-by: Dima Arnautov <dmitrii.arnautov@elastic.co>	2022-11-21 12:00:28 -07:00
Kibana Machine	bc3f322a3c	[8.6] [ML] Explain Log Rate Spikes: Use bulk indexing for dummy data. (#145699) (#145716) ... # Backport This will backport the following commits from `main` to `8.6`: - [[ML] Explain Log Rate Spikes: Use bulk indexing for dummy data. (#145699)](https://github.com/elastic/kibana/pull/145699) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Walter Rafelsberger","email":"walter.rafelsberger@elastic.co"},"sourceCommit":{"committedDate":"2022-11-18T11:49:06Z","message":"[ML] Explain Log Rate Spikes: Use bulk indexing for dummy data. (#145699)\n\nThe functional tests added 100 docs with individual requests. This\r\nupdate uses bulk indexing to speed up preparing the data.","sha":"65a9b0950548c2b3cac302f6bdad1532cd032260","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":[":ml","release_note:skip","Feature:ML/AIOps","v8.6.0","v8.7.0"],"number":145699,"url":"https://github.com/elastic/kibana/pull/145699","mergeCommit":{"message":"[ML] Explain Log Rate Spikes: Use bulk indexing for dummy data. (#145699)\n\nThe functional tests added 100 docs with individual requests. This\r\nupdate uses bulk indexing to speed up preparing the data.","sha":"65a9b0950548c2b3cac302f6bdad1532cd032260"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/145699","number":145699,"mergeCommit":{"message":"[ML] Explain Log Rate Spikes: Use bulk indexing for dummy data. (#145699)\n\nThe functional tests added 100 docs with individual requests. This\r\nupdate uses bulk indexing to speed up preparing the data.","sha":"65a9b0950548c2b3cac302f6bdad1532cd032260"}}]}] BACKPORT--> Co-authored-by: Walter Rafelsberger <walter.rafelsberger@elastic.co>	2022-11-18 05:41:43 -07:00
Kibana Machine	a8164ed83c	[8.6] [DOCS] Automate connector-listing.png (#143605) (#145659) ... # Backport This will backport the following commits from `main` to `8.6`: - [[DOCS] Automate connector-listing.png (#143605)](https://github.com/elastic/kibana/pull/143605) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Lisa Cawley","email":"lcawley@elastic.co"},"sourceCommit":{"committedDate":"2022-11-18T01:08:41Z","message":"[DOCS] Automate connector-listing.png (#143605)\n\nCo-authored-by: Robert Oskamp <traeluki@gmail.com>","sha":"31ca6447332e52e502f0ed3645ebb02f054807c7","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:ResponseOps","docs","v8.6.0","v8.5.1","v8.7.0"],"number":143605,"url":"https://github.com/elastic/kibana/pull/143605","mergeCommit":{"message":"[DOCS] Automate connector-listing.png (#143605)\n\nCo-authored-by: Robert Oskamp <traeluki@gmail.com>","sha":"31ca6447332e52e502f0ed3645ebb02f054807c7"}},"sourceBranch":"main","suggestedTargetBranches":["8.6","8.5"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.5","label":"v8.5.1","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/143605","number":143605,"mergeCommit":{"message":"[DOCS] Automate connector-listing.png (#143605)\n\nCo-authored-by: Robert Oskamp <traeluki@gmail.com>","sha":"31ca6447332e52e502f0ed3645ebb02f054807c7"}}]}] BACKPORT--> Co-authored-by: Lisa Cawley <lcawley@elastic.co>	2022-11-17 19:46:30 -07:00
Kibana Machine	18a876db48	[8.6] [Stack Monitoring] api tests for kibana (#145230) (#145527) ... # Backport This will backport the following commits from `main` to `8.6`: - [[Stack Monitoring] api tests for kibana (#145230)](https://github.com/elastic/kibana/pull/145230) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Kevin Lacabane","email":"kevin.lacabane@elastic.co"},"sourceCommit":{"committedDate":"2022-11-17T10:25:24Z","message":"[Stack Monitoring] api tests for kibana (#145230)\n\n## Summary\r\nPart of https://github.com/elastic/kibana/issues/119658\r\n\r\nAdd api integration tests for kibana routes to validate behavior when\r\nreading data ingested by elastic-agent.\r\n\r\nWe currently have a testing suite for legacy and another one for\r\nmetricbeat. Since metricbeat and agent documents only differ in their\r\nmetadata, for example agent will populate a `data_stream.*` property to\r\nidentify the document types while metricbeat uses `metricset.*`, the\r\ntests assertion validating _business_ data should pass regardless of the\r\ndocuments source. With this in mind the metricbeat tests were updated to\r\nrun the tests twice, one time with metricbeat data and a second time\r\nwith package data.\r\n\r\nTo generate the archives the `metrics-*` mappings were extracted with\r\nesArchiver from an elasticsearch with the package installed, and the\r\ndocuments were transformed from the metricbeat documents with [this\r\nscript](https://gist.github.com/klacabane/654497ff86053c60af6df15fa6f6f657).\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"90f0ae2966016e0a010caedc9c83d02947d4f4f0","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Infra Monitoring UI","release_note:skip","Feature:Stack Monitoring","v8.6.0","v8.7.0"],"number":145230,"url":"https://github.com/elastic/kibana/pull/145230","mergeCommit":{"message":"[Stack Monitoring] api tests for kibana (#145230)\n\n## Summary\r\nPart of https://github.com/elastic/kibana/issues/119658\r\n\r\nAdd api integration tests for kibana routes to validate behavior when\r\nreading data ingested by elastic-agent.\r\n\r\nWe currently have a testing suite for legacy and another one for\r\nmetricbeat. Since metricbeat and agent documents only differ in their\r\nmetadata, for example agent will populate a `data_stream.*` property to\r\nidentify the document types while metricbeat uses `metricset.*`, the\r\ntests assertion validating _business_ data should pass regardless of the\r\ndocuments source. With this in mind the metricbeat tests were updated to\r\nrun the tests twice, one time with metricbeat data and a second time\r\nwith package data.\r\n\r\nTo generate the archives the `metrics-*` mappings were extracted with\r\nesArchiver from an elasticsearch with the package installed, and the\r\ndocuments were transformed from the metricbeat documents with [this\r\nscript](https://gist.github.com/klacabane/654497ff86053c60af6df15fa6f6f657).\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"90f0ae2966016e0a010caedc9c83d02947d4f4f0"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/145230","number":145230,"mergeCommit":{"message":"[Stack Monitoring] api tests for kibana (#145230)\n\n## Summary\r\nPart of https://github.com/elastic/kibana/issues/119658\r\n\r\nAdd api integration tests for kibana routes to validate behavior when\r\nreading data ingested by elastic-agent.\r\n\r\nWe currently have a testing suite for legacy and another one for\r\nmetricbeat. Since metricbeat and agent documents only differ in their\r\nmetadata, for example agent will populate a `data_stream.*` property to\r\nidentify the document types while metricbeat uses `metricset.*`, the\r\ntests assertion validating _business_ data should pass regardless of the\r\ndocuments source. With this in mind the metricbeat tests were updated to\r\nrun the tests twice, one time with metricbeat data and a second time\r\nwith package data.\r\n\r\nTo generate the archives the `metrics-*` mappings were extracted with\r\nesArchiver from an elasticsearch with the package installed, and the\r\ndocuments were transformed from the metricbeat documents with [this\r\nscript](https://gist.github.com/klacabane/654497ff86053c60af6df15fa6f6f657).\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"90f0ae2966016e0a010caedc9c83d02947d4f4f0"}}]}] BACKPORT--> Co-authored-by: Kevin Lacabane <kevin.lacabane@elastic.co>	2022-11-17 04:15:47 -07:00
Quynh Nguyen (Quinn)	22d0fa742d	[ML] Switch from normal sampling to random sampler for Index data visualizer table (#144646) ... Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>	2022-11-16 08:36:55 -06:00
Jeramy Soucy	8070fae769	Unskip Spaces Navigation Tests (#144700) ... Closes #142155. Unskips the spaces navigation tests reported failing in #142155. Ran locally and with a [flaky test runner](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/1552) and could not reproduce the issue.	2022-11-16 08:25:03 +01:00
Marshall Main	a2647ab67c	[Security Solution][Alerts] Alert suppression per rule execution (#142686) ... ## Summary Addresses https://github.com/elastic/kibana/issues/130699 This PR implements alert throttling per rule execution for query and saved query rules. The implementation is very similar in concept to threshold rules. We allow users to pick one or more fields to group source documents by and use a composite aggregation to collect documents bucketed by those fields. We create 1 alert for each bucket based on the first document in the bucket and add metadata to the alert that represents how to retrieve the rest of the documents in the bucket. The metadata fields are: - `kibana.alert.suppression.terms`: `{field: string; value: Array<string | number>}` An array of objects, each object represents one of the terms used to group these alerts - `kibana.alert.suppression.start`: `Date` The timestamp of the first document in the bucket - `kibana.alert.suppression.end`: `Date` The timestamp of the last document in the bucket - `kibana.alert.suppression.docs_count`: `number` The number of suppressed alerts There is one new rule parameter, currently implemented at the solution level, to enable this feature: `alertSuppression.groupBy`: `string[]`. Similar to threshold rules, the throttled query rules keep track of created alerts in the rule state in order to filter out duplicate documents in subsequent rule executions. When a throttled alert is created, we store the bucket information including field names, values, and end date in the rule state. Subsequent rule executions convert this state into a filter that excludes documents that have already been covered by existing alerts. This is necessary because consecutive rule executions will typically query overlapping time ranges. ## Screenshots ### Rule Create/Edit With License <details>  </details> ### Rule Details With License <details>  </details> ### Rule Create, or Rule Edit of a rule without existing suppression configuration, Without License <details>  </details> ### Editing a rule that has existing suppression configuration, but without the correct license, still allows changing the configuration (to allow removing the params) <details>  </details> ### Rule Details Without License <details>  </details> ### Alerts table <details>  </details> ### Known issues - The layers icon in the rule name for suppressed alerts does not show up in the rule preview table Co-authored-by: Madi Caldwell <madison.caldwell@elastic.co> Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>	2022-11-15 11:08:41 -08:00
Stratoula Kalafateli	928674a39c	[TSVB] Wait for stabilization on the table to lens transition (#145209) ... Closes https://github.com/elastic/kibana/issues/145127 I feel that waiting for stabilization will fix the flakiness here 100 times runner https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/1551	2022-11-15 17:43:23 +02:00
Dima Arnautov	ca49da1470	[ML] Allow updates for number of allocations and priority for trained model deployments (#144704) ... ## Summary Resolves #144550 and #144595 Adds a new action to the Trained Models table to update the number of allocations for already started deployments. <img width="1422" alt="image" src="https://user-images.githubusercontent.com/5236598/200321473-0b869084-6c25-4873-8409-b948b7bede50.png"> Sets priority while starting a deployment <img width="1278" alt="image" src="https://user-images.githubusercontent.com/5236598/200596233-a884d271-fefb-4898-9f2f-8d4724d25484.png">	2022-11-15 09:59:57 +01:00
Xavier Mouligneau	e9feb06550	[RAM] Update rule status (#140882) ... ## Summary Resolves the parent issue: https://github.com/elastic/kibana/issues/136039 Also resolves the subtasks: - https://github.com/elastic/kibana/issues/143461 - https://github.com/elastic/kibana/issues/143460 This is the backend portion of the consolidated rule status feature. It mainly contains changes to the `rules_client.ts` and `task_runner.ts` to support the new consolidated rule statuses. This PR added a new property: `lastRun` to the rules saved object to hold the new rule outcome statuses (`succeeded`, `warning`, and `failed`) as the new simplified rule status over the existing `executionStatus` property. However, we are keeping the old `executionStatus` so we can slowly migrate the rest of the application to use the new `lastRun` outcomes. In addition, we have enriched the `monitoring` property to be the source of truth for metrics related to the last run (as well as new fields that other plugins will find useful). We also added a monitoring service that allows other plugins to easily add data to the monitoring field. To test this PR, please use https://github.com/elastic/kibana/pull/144466 since it has both the frontend and backend changes. ### Checklist - [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> Co-authored-by: Jiawei Wu <jiawei.wu@cmd.com>	2022-11-14 13:21:58 -07:00
Vitalii Dmyterko	f1117c8959	[Security Solution][Alerts] adds support for multi fields in new terms rule (#143943) ... ## Summary - addresses https://github.com/elastic/kibana/issues/142862 - allows up to 3 fields in `New terms` - displays new terms fields in alerts details - For multiple new terms fields(['source.host', 'source.ip']), in terms aggregation uses a runtime field. Which is created by joining values from new terms fields into one single keyword. Field values encoded in base64 and joined with a configured delimiter symbol, which is not part of base64 symbols(a–Z, 0–9, +, /, =) to avoid a situation when delimiter can be part of field value. Include parameter consists of encoded in base64 results from Phase 1. For single field, implementation remains the same to avoid performance penalties - Performance measurements: - [msearch POC for one field](https://github.com/elastic/kibana/pull/131010#issuecomment-1135280478) - [historical POC of multi fields](https://github.com/elastic/kibana/issues/142862#issuecomment-1290471400) - [current implementation](https://github.com/elastic/kibana/issues/142862#issuecomment-1298910940) ## UI ### Alert details #### Before <img width="1128" alt="Screenshot 2022-10-26 at 18 29 00" src="https://user-images.githubusercontent.com/92328789/199074598-33483312-a660-49e2-aab6-9aea4f70a23e.png"> #### After <img width="1129" alt="Screenshot 2022-11-09 at 19 05 10" src="https://user-images.githubusercontent.com/92328789/201698130-b907a200-3cdd-49e6-ae76-a5e0ef9a9450.png"> Delete any items that are not applicable to this PR. - [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios ### For maintainers - [ ] This was checked for breaking API changes and was [labeled appropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)	2022-11-14 09:55:20 -07:00
John Dorlus	045b57093c	CCS Tests for Machine Learning (#144869)	2022-11-14 11:31:27 -05:00
Stratoula Kalafateli	a5cfe8ec0d	[Lens] Hide the random sampling settings from the UI (#145071) ... ## Summary Hides the random sampling layer settings from the UI until we decide how we want to introduce it to our users.	2022-11-14 16:14:21 +02:00
Sergi Massaneda	6bba30f94c	[Security Solution] Tines connector (#143505) ... ## Summary Issue: https://github.com/elastic/kibana/issues/140066 Doc: https://docs.google.com/document/d/14BY-6CIin1CUH5bwJJgfrGl37hWO-CeNMdl_35agpvk/edit?usp=sharing Create a new connector type that offers low friction/low effort approach to augmenting Elastic capabilities with SOAR capabilities of Tines. ## Implementation Tines connector implements subActionConnector. With 4 subActions configured: - **stories**: Retrieves the User available Story objects from Tines, to render the Story selector options in the params form. It uses the `email` and `token` authentication headers from the configuration. It is requested only when the form opens and when the connector instance changes. - **webhooks**: Retrieves the Story available Webhooks objects from Tines, to render the Webhook selector in the params form. It uses the `email` and `token` authentication headers from the configuration and the `story_id` parameter. There is no filter for `type` in the actions (a.k.a. agents) endpoint, so we have to request all actions and filter them by `type === 'Agents::WebhookAgent'` on our side. It is requested every time the selected story changes. - **run**: The main action execution. It sends the alerts to the Tines configured webhook, using webhook' `path` and `secret` values. There's no template to render, the data coming from the execution is just pruned (the `kibana` entry is removed from all `context.alerts`) and sent directly using the same format to Tines. - **test**: The test form execution. It ends up calling **run** but using a parametrized body. ### Pagination Both **stories** and **webhooks** subActions need pagination, since Tines do not expose any search endpoint for them. The current hard limit is 100 pages. The `paginatedRequest` function in the connector implementation encapsulates this logic. ## Testing 1- Create a [Tines](https://www.tines.com/) free account. 2- Create a [new Story](https://www.tines.com/docs/quickstart/simple-story) and attach a [Webhook Action](https://www.tines.com/docs/quickstart/creating-an-action) to start receiving events. 3- Create an [API token](https://www.tines.com/api/authentication) 4- Configure the Tines Connector in Kibana using the Tines tenant URL that has been generated in the Tines app, the email used to sign in, and the API token generated. [docs](https://github.com/semd/kibana/blob/140066_tines_connector/docs/management/connectors/action-types/tines.asciidoc#connector-configuration) 5- Attach the Tines Connector to a Detection Rule, selecting the Story and Webhooks created. [docs](https://github.com/semd/kibana/blob/140066_tines_connector/docs/management/connectors/action-types/tines.asciidoc#actions) 6- After each rule execution, events should appear in the Tines webhook action. ## Screenshots Configure a Tines connector   Use the Tines connector   Tines events  ### Checklist Delete any items that are not applicable to this PR. - [x] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md) - [x] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios(https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US)) Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> Co-authored-by: Jonathan Buttner <56361221+jonathan-buttner@users.noreply.github.com>	2022-11-14 13:04:47 +01:00
Bena Kansara	74a2b37631	Adds list of containers in context variable of Inventory rule (#144526) ... ## Summary Closes https://github.com/elastic/kibana/issues/143727 When Inventory rule is created for `Kubernetes Pods` as node type, the `context.container` will contain an array of containers. For other node types, the `context.container` will contain single container information. This is to cover the use case where Kubernetes pod has more than one container. ## Manual testing ### 1. Create rule for `Kubernetes Pods` - Create Inventory rule for `Kubernetes Pods` - Select a connector to schedule action - Add `{{context}}` in the action template - Wait for alerts to be generated - Observe `context.container` lists all containers <img width="803" alt="Screenshot 2022-11-04 at 10 55 19" src="https://user-images.githubusercontent.com/69037875/199945124-08590d1e-50ed-4b41-a256-8b16548dbdbd.png"> ### 2. Create rule for `Hosts` - Create Inventory rule for `Hosts` - Select a connector to schedule action - Add `{{context}}` in the action template - Wait for alerts to be generated - Observe `context.container` contains single container <img width="520" alt="Screenshot 2022-11-04 at 10 59 31" src="https://user-images.githubusercontent.com/69037875/199945890-a38a695a-61bc-49cb-9eb4-6fa806f4bdc9.png"> ### Checklist - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>	2022-11-10 19:24:03 +01:00
Robert Oskamp	cf281d61ca	[ML] Functional tests - stabilize and re-enable test suites (#144784) ... This PR stabilizes and re-enables a few ML functional test suites.	2022-11-10 10:35:40 +01:00
Felix Stürmer	c88a680c60	[Logs UI] Use the Unified Search Bar for date range selection (#144351) ... This enables the date-picker of the unified search bar introduced into the Logs UI in #143222 and simultaneously removes the custom date picker. closes https://github.com/elastic/kibana/issues/142767	2022-11-09 18:49:32 +01:00
Tiago Costa	c3f5b6aba5	skip flaky suite (#144885)	2022-11-09 14:08:57 +00:00
Ahmad Bamieh	62425648c7	[Upgade Assistant] Enable UA for minor upgrades (#143544) ... Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>	2022-11-08 18:57:42 -07:00
Christos Nasikas	c73dc349ae	[Cases] Tags bulk & row actions (#143450) ... ## Summary This PR adds the ability to bulk edit tags from the cases table. It also adds the tag row action to edit tags on an individual case. ## User flow https://user-images.githubusercontent.com/7871006/199962211-cb57f34d-1319-4008-b204-7adee623c9e4.mov ## Screenshots <img width="1922" alt="Screenshot 2022-11-04 at 1 29 15 PM" src="https://user-images.githubusercontent.com/7871006/199962454-663d163b-f1a6-4fd5-a5df-d2e5b1704f4f.png"> <img width="479" alt="Screenshot 2022-11-04 at 1 30 01 PM" src="https://user-images.githubusercontent.com/7871006/199962445-b1194e1b-efff-4fdd-8e50-1fa4bef7c960.png"> <img width="482" alt="Screenshot 2022-11-04 at 1 29 29 PM" src="https://user-images.githubusercontent.com/7871006/199962452-5664a4fd-459d-422c-b08c-c9f00ea88190.png"> ### Checklist Delete any items that are not applicable to this PR. - [x] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md) - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [x] This renders correctly on smaller devices using a responsive layout. (You can test this [in your browser](https://www.browserstack.com/guide/responsive-testing-on-local-server)) - [x] This was checked for [cross-browser compatibility](https://www.elastic.co/support/matrix#matrix_browsers) ### For maintainers - [x] This was checked for breaking API changes and was [labeled appropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) ## Release notes Add the ability to bulk edit tags in the cases table	2022-11-08 20:03:00 +02:00
Melissa Alvarez	c53ddb7c85	[ML] Data Frame Analytics: Add brushing to link docs in scatterplot charts (#144354) ... ## Summary Related meta issue: https://github.com/elastic/kibana/issues/131551 In this PR support is added for selecting/highlighting an area in one scatterplot chart highlighting the corresponding area in the rest of the charts. - adds `user_selection` to spec - adds `user_selection` condition in `encoding` `color` to ensure highlighting in corresponding area of other charts - outlier and user selection (by drag or single point click) are now different colors #### Classification results: <img width="929" alt="image" src="https://user-images.githubusercontent.com/6446462/200012485-18cee3f9-8180-4727-894c-6d8376678c03.png"> #### Classification job wizard: <img width="928" alt="image" src="https://user-images.githubusercontent.com/6446462/200013588-2445f475-274c-4548-bcc3-4af4d631a6c4.png"> #### Outlier Detections results: <img width="969" alt="image" src="https://user-images.githubusercontent.com/6446462/200036149-4491ea6e-77a5-4c1b-9ddc-386d8a492f69.png"> #### Outlier Detection job wizard: <img width="938" alt="image" src="https://user-images.githubusercontent.com/6446462/200036269-b3b8ce39-6956-4bf9-b7ff-f61eb2022ae8.png"> #### Regression results: <img width="922" alt="image" src="https://user-images.githubusercontent.com/6446462/200013085-248eff9a-09f5-42a3-ac11-c2bfc3c08cf4.png"> #### Regression job wizard: <img width="944" alt="image" src="https://user-images.githubusercontent.com/6446462/200013485-0c54808c-2cc2-44e6-bc6d-bb1c3825cbe8.png"> ### Checklist Delete any items that are not applicable to this PR. - [ ] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md) - [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [ ] Any UI touched in this PR is usable by keyboard only (learn more about [keyboard accessibility](https://webaim.org/techniques/keyboard/)) - [ ] Any UI touched in this PR does not create any new axe failures (run axe in browser: [FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/), [Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US)) - [ ] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker) - [ ] This renders correctly on smaller devices using a responsive layout. (You can test this [in your browser](https://www.browserstack.com/guide/responsive-testing-on-local-server)) - [x] This was checked for [cross-browser compatibility](https://www.elastic.co/support/matrix#matrix_browsers) Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>	2022-11-08 11:23:42 -05:00
Joe Reuter	4107da864c	[TSVB] Adjust tolerance of screenshot (#144804) ... Fixes https://github.com/elastic/kibana/issues/138814 by updating the baseline and reducing the tolerance	2022-11-08 17:12:27 +01:00
Bena Kansara	dffa38427a	Adds new contextual attributes to Infrastructure - Metric threshold rule (#143001) ... * creating alert link with alert id and rule id * Revert "creating alert link with alert id and rule id" This reverts commit 29bede6aab. * additional context variables for metric threshold rule * [CI] Auto-commit changed files from 'node scripts/eslint --no-cache --fix' * fixing type error * changed description of context variables * adding context only if group by is available, creating container list * refactoring, fixing types * fixing CI error * fixed issues * refactoring * fixing failing tests * refactoring, fixing tests * added tests, refactoring * fixing issue with group by * fixing failing tests * fixing failing tests * [CI] Auto-commit changed files from 'node scripts/precommit_hook.js --ref HEAD~1..HEAD --fix' * [CI] Auto-commit changed files from 'node scripts/eslint --no-cache --fix' * [CI] Auto-commit changed files from 'node scripts/precommit_hook.js --ref HEAD~1..HEAD --fix' * fixing failing tests * [CI] Auto-commit changed files from 'node scripts/eslint --no-cache --fix' * refactoring * [CI] Auto-commit changed files from 'node scripts/precommit_hook.js --ref HEAD~1..HEAD --fix' Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>	2022-11-08 13:56:57 +01:00
Tiago Costa	32f514e819	skip flaky suite (#143007)	2022-11-07 23:08:08 +00:00
Bree Hall	4e9f1c0d04	Bumping EUI to version 67.1.8 (#141279) ... * Updated EUI to version 67.1.2. Updated instaces of ButtonColor from EUI to EuiButtonColor. * Updated to EuiCard instances that utilize the betaBadgeProps object to return an empty string instead of undefined when the label is unavailable * Removed two instances of the deprecated internetExplorerOnly() mixin * Updated two instances of the ButtonColor import to EuiButtonColor as is was renamed in PR #6150 * Updated snapshots in Jest Test Suite #1 to account for EuiButton and EuiCard Emotion conversions. Updated snapshots for EuiTooltip as it now contains the new EuiToolTipAnchor component that replaced the tooltip anchor styles * Updated snapshots in Jest Test Suite #2 to account forEuiButton, EuiDescriptionList, EuiButtonIcon, and EuiBadge Emotion conversions. * Updated snapshots in Jest Test Suite #3 to account for EuiDescriptionList, EuiButton, and EuiBadge Emotion conversions. Updated snapshots for EuiTooltip as if now contains the new EuiTooltipAnchor component that replaced the tooltop anchor styles * Updated snapshots in Jest Test Suite #4 to account for EuiButton Emotion conversion. * Updated snapshots in Jest Test Suite #5 to account for EuiButton Emotion conversion. * Updated snapshots in Jest Test Suite #8 to account for EuiButtonIcon and EuiButton Emotion conversions. Updated snapshots for EuiTooltip as it now contains the new EuiTooltipAnchor component that replaced the tooltip anchor styles. * Updated snapshots in Jest Test Suite #9 to account for EuiFlyout and EuiButton Emotion conversions. * Updated snapshots in Jest Test Suite #10 to account for EuiButton, EuiBadge, EuiButtonIcon, and EuiCard Emotion conversions. Updated snapshots for EuiToolTtip as it now contains the new EuiTooltipAnchor component that replaced the tooltip anchor styles * Updated instances of EuiButtonIconColor to use EuiButtonIconProps['color'] as it was removed in PR #6150 * Updated tests that target EuiButton to simulate click events to target a generic button to prevent undefined click event errors * Updated snapshots in Jest Test Suite #1 to account for EuiButton and EuiCard Emotion conversions * Added the EuiFlyout mixins and variables to Lens Sass file as EuiFlyout has been converted to Emotion and the Sass styles are no longer available in EUI * Added the EuiCallOutTypes variable to Step Progress Sass file as EuiCallOut has been converted to Emotion and the Sass styles are no longer available in EUI * Updated snapshots in Jest Test Suite #2 to account for recent Emotion conversions. Updated snapshots in server_status.test.tsx to render EuiBadge before checking the snapshots to reduce the snapshot churn caused by Emotion. Updated tests that target EuiButton to simulate click events to target a generic button to prevent undefined click event errors * [CI] Auto-commit changed files from 'node scripts/precommit_hook.js --ref HEAD~1..HEAD --fix' * Added imports for the added flyout mixin. Removed references to EuiCallOut mixin as the component has been converted to Emotion and is no longer available for use. * Updated unit tests and snapshots in Jest Test Suite #10. Updated snaphshots to account for EuiBadge, EuiDescriptionList, EuiFlyout, and EuiCard Emotion conversions. Updated snapshots for EuiTooltip as it now contains the new EuiTooltipAnchor component that replaced the tooltip anchor styles. Updated tests that target EuiButton to simulate click events to target a generic button element to prevent undefined click event errors * Updated unit tests in Jest Test Suite #11 that target EuiButton to simulate click events to target a generic button to prevent undefined click event errors * Updated unit tests in Jest Test Suite #12 by updating tests that target EuiButton to simulate click events. Instead, these tests now target a generic button element to prevent undefined click event errors * Updated unit tests in Jest Test Suite #1 by updating tests that target EuiButton to simulate click events. Instead, these tests now target a generic button element to prevent undefined click event errors * Updated unit tests in Jest Test Suite #2 by updating tests that use EuiButton to simulate click events. Instead, these test have been updated to target a button element to prevent undefined click event errors. * [CI] Auto-commit changed files from 'node scripts/eslint --no-cache --fix' * Updated reference to mixins Sass file. Updated snapshots for Jest Test Suite #5 to account for EuiButton Emotion conversion. Updated unit tests that target EuiButton to simulate click events. These tests have been updated to target a button element to prevent undefined click event errors * Updated unit tests in Jest Test Suites 3, 7, 8, 13, and 14. Updated snapshot to account for EuiButton Emotion conversion. Updated tests that target EuiButton to simulate click events. These tests now target a generic button element to prevent undefined click event errors. Updated a few snapshots by adding .render() before checking the snapshot. This will prevent large snapshots coming from recent Emotion conversions * Updated snapshots in Jest Test Suite #10 to account for the recent EuiButton Emotion conversion * Updated unit tests in Jest Test Suite #2 by editing tests that target EuiButton to simulate click events. These tests now target a button element in order to prevent undefinde click event errors * Updated snapshots in Jest Test Suite #10 to account for EuiButton and EuiDescriptionList Emotion conversions * Updated test cases in Jest Test Suites 3, 7, and 8. Updated snapshots to account for EuiButton and EuiPagination Emotion conversions. Updated tests that target EuiButton to simulate click events. These tests now target a button element to prevent undefined click errors * Updated test cases in Jest Test Suite 14. Updated snapshots to account for EuiButton Emotion conversion. Opted to use .render() when updating a few snapshots to reduce the large length of snapshots caused by Emotion * [CI] Auto-commit changed files from 'node scripts/eslint --no-cache --fix' * Revised a change to betaBadgeProps to ensure that the label is available. If not, the value for the badge with be set to undefined. * Resolved two linting errors * Resolved two linting errors * Updated Jest unit tests in various suites. Updated snapshots to account for EuiButton Emotion conversion. Updated snapshots for EuiTooltip as it now contains the new EuiTooltipAnchor component that replaced the tooltip anchor styles. * Updated EuiFlyout in query_flyout.tsx to remove the onClick function from maskProps as it is no longer available. Updated this flyout to use ownFocus and not to close when the overlay mask is clicked. * Removed the use of EuiButtonIconColor in favor of EuiButtonIconProps['color'] * [CI] Auto-commit changed files from 'node scripts/eslint --no-cache --fix' * Updated Cypress test looking for strict equality on EuiPaginationButton class names to match a substring of the Emotion generated class name * Removed unneeded debugging code. Updated snapshots for various test suites to account for the recent EuiButton Emotion conversion * Updated a few EuiButton, EuiButtonEmpty, and EuiText components that set the color as ghost. The ghost color mode has been deprecated as of PR #6150. These components now are wrapped in EuiThemeProvider with a dark colorMode to create the previous ghost color. * Resolved TS error with EuiCard betaBadgeProps * [CI] Auto-commit changed files from 'node scripts/eslint --no-cache --fix' * Remove references to now-removed EuiFlyout CSS classes/vars * Remove now-removed euiBadge className references - Convert directly to EuiBadge instead of using CSS - Remove confusing and now-possibly-irrelevant CSS badge overrides - left/right icons are now set via JSX and not via flex-direction * Pre-emptively fix various euiOverlayMask CSS overrides - this data attr isn't technically in yet but will be once https://github.com/elastic/eui/pull/6289 merges - at the very least this isn't breaking any more than it currently already is! * Update to v67.1.3 * v67.1.4 * Resolved test failing test case in Security/Manage/Blocklist. The test did not remove focus from the last combo box in the form, which didn't allow the disbaled attribute to be removed from the flyout submit button. I've updated the mock file for Blocklist to return focus to the first form element in the flyout to allow the disabled attribute to be removed. * Updated snapshots to account for the recent EuiText Emotion conversion * Fix Log's custom tooltips relying on EuiTooltip classNames that no longer exist * Fix Vega vis custom tooltips relying on EuiTooltip classNames that no longer exist - this one is trickier than Log's as it's not using React, so we need to use Emotion's Global to set a static className * Convert remaining vega_vis.scss to Emotion - as an example of how other global + non global styles could be handled in the future * Fix references to removed `euiPaginationButton-isActive` className - use aria-current attribute instead * Added missing EuiFlyoutAnimation keyframes for EuiFlyout. This resolved test that failed because they used onAnimationEnd because the FlyoutAnimation could not be found. * Reolved Jest Tests in suites 1 and 5. Updated snapshots to account for the recent EuiButton Emotion conversion. Updated snapshots for EuiToolTip as it now contains the new EuiToolTipAnchor component that replaced the tooltip anchor styles. * iterate on rules_list.test.tsx * bump eui to v67.1.5 * Updatde snapshots for jest test suites to account for the recent EuiButton, EuiOverlayMask, EuiTooltip, and EuiBadge Emotion conversions * Resolved failing security test by updating the target element for CONNECTOR_TITLE. EuiCard has recently been converted to Emotion and the card title is no longer wrapper in a span. * Resolved failing test case in Runtime Fields. The modify runtime field test was failing because the combobox responsbible for adding and updating scripts was not appearing. The textbox did not appear because the shared setFieldScript function targets and toggles the script textbox when opening the flyout. When a runtime field is being modified, the toggle is already active and using the shared function will trigger the toggle again (losing access to the script textbox). Also resolved an issue that prevented the warning EuiCallout to appear when changing the type of a runtime field from its original type. Resolved this by adding an enter keypress at the end of setFieldType function to confirm the type selection, thus triggering the EuiCallout * Resolved two tests that were failing in Lens. These test were failing because they were checking for equality in class names that no longer exist within EuiButtonGroup as it was recently converted to Emotion. These tests were updated to check for a substring of the new and longer class name * Quick fix in test case failing because of misspelling in data-test-sub * Updated snapshot for Jest test case as EuiButton as recently been converted to Emotion * Removed console.log statement. Oops! * Resolved a failing test case in Lens. They were failing because they were checking for equality in class names that no longer exist within EuiButtonGroup as it was recently converted to Emotion. These tests were updated to check for a substring of the new and longer class name. Updated a Security test case by giving a target button the data-test-subj attribute for easier querying * Removed reference to EuiFlyout mixin as it has been converted to Emotion. Updated the reference to an interal copy of EuiFlyout styles * Corrected spelling error in EuiFlyout animation in Lens app * Update EUI with latest backport * Update button snapshots * fix another button snapshot * More snapshot fixes * [EuiButton][Security] Fix button relying on now-removed `euiButton__text` CSS - replace removed CSS with `eui-textTruncate` util instead - combine/DRY out unnecessary span - was affecting min-width of truncation util + increase screenshot diff limit - this was smaller than updating the actual baseline screenshots for whatever reason (likely render diff between local and CI) * Fix remaining Jest tests affected by Emotion conversions - because Emotion creates its own wrapper, `.first()` can no longer be used - prefer `.last()` instead * Fix Jest test affected by EuiButton Emotion conversion + removed modifier class - targeting the native DOM node + filtering by disabled true/false gets us back to the 'correct' lengths * Fix + improve flyout test - `.last()` changes to account for EuiButton Emotion conversion is needed, but the last onClose assertion still fails due to us having modified inputs, and the confirm modal being displayed - split test into two separate tests - one testing the onClose call, and the other testing the confirm modal * derpin * Skip rules_list Jest suite * Update new EuiButton snapshot * Upgraded EUI version to 67.1.7 * [EuiCard] Update snapshots * [EuiPopover] Update snapshots * [QA] Fix missing Vega warn/error message colors ;_; * [CI] Auto-commit changed files from 'node scripts/generate codeowners' * Fix Lens kbnToolbarButton regressions - Caused by flattening of EUI button CSS specificity - background-color was previously relying on isDisabled CSS specificity to override its #fff color - `text` color modifier & `!important` is no longer needed and overrides Emotion CSS flatly - isDisabled class is no longer needed - euiButton no longer sets `pointer-events: none` on disabled buttons (fixes tooltip bug in webkit as well) * Backport EUI 67.1.8 fixes * Update EuiCard snapshots * Fix EuiModal form wrapper causing overflow issues - see https://elastic.github.io/eui/#/layout/modal#forms-in-a-modal * Workaround for `.kbnOverlayMountWrapper` mount point causing overflow issues - not sure what all is using this modal service to be honest, but the wrapper is causing issues with the modal layout, this fixes overflow issues but will not fix any mask-image issues as a result * more snapshot updates * EuiButton - added textProps to EuiButton to prevent very long button names from spilling over outside of the container * EuiButton - Update EuiButton related snapshots. Updated tests that target EuiButton directly to use a data-telementary-id for more specific element querying required by Emotion * QA - Removed unnecessary comment in code * Temporary fix for EuiCard[selectable][layout=horizontal] instances on security solutions' rule page * Temporary fix for EuiCard[selectable][layout=horizontal] instances on osquery live query and canvas's datasource selector * [CI] Auto-commit changed files from 'node scripts/precommit_hook.js --ref HEAD~1..HEAD --fix' * Fix CSS specificity, where canvas's solutionToolbarButton's background-color now takes precedence over EuiButton's primary styles * Removed update to search_marker_tooltip that removed the euiTooltip styles and replaced then with Emotion styling. Added EuiTooltip Sass styles for the component to rely on to test for a styling bug that is causing the tooltip and the tooltip arrow to be out of sync with each other. * Lint Sass file * Lint Sass file * Removed overflow:hidden style from .vgaVis_view as it was causing euiScrollStyles not to present the scroll bars in Vega Vis * Remove typo from EuiButton textProps object. 'className' should not have been included in the actual class name * Revert tooltip Sass This reverts commit 20e6ead571, a5cd2de901, and c605cbd7b9 * Fix Emotion tooltip arrows Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> Co-authored-by: Constance Chen <constance.chen@elastic.co> Co-authored-by: Chandler Prall <chandler.prall@elastic.co>	2022-11-07 21:45:50 +00:00
Jonathan Buttner	ae9dd59137	[ResponseOps][Stack Connectors] Opsgenie UI phase 2 (#143480) ... * Starting opsgenie backend * Adding more integration tests * Updating readme * Starting ui * Adding hash and alias * Fixing tests * Switch to platinum for now * Adding server side translations * Fixing merge issues * Fixing file location error * Working ui * Default alias is working * Almost working validation fails sometimes * Adding end to end tests * Adding more tests * Adding note and description fields * Removing todo * Adding in advanced sections * Adding tags and finish mode * Working editor and toggle * [CI] Auto-commit changed files from 'node scripts/precommit_hook.js --ref HEAD~1..HEAD --fix' * Refactoring code * Adding tests * Fixing tests and reordering input fields * Using io-ts for schema validation in ui * Adding more e2e tests and clean up * Fixing type errors * Adding spacing and label * Adding more tests and fixing come failure message errors * Making json editor errors more readable * Fixing errors and adding docs * Updating enabled action types * Update docs/management/connectors/action-types/opsgenie.asciidoc Co-authored-by: nastasha-solomon <79124755+nastasha-solomon@users.noreply.github.com> * Update docs/management/connectors/action-types/opsgenie.asciidoc Co-authored-by: nastasha-solomon <79124755+nastasha-solomon@users.noreply.github.com> * Update docs/management/connectors/action-types/opsgenie.asciidoc Co-authored-by: nastasha-solomon <79124755+nastasha-solomon@users.noreply.github.com> * Update docs/management/connectors/action-types/opsgenie.asciidoc Co-authored-by: nastasha-solomon <79124755+nastasha-solomon@users.noreply.github.com> * Update docs/management/connectors/action-types/opsgenie.asciidoc Co-authored-by: nastasha-solomon <79124755+nastasha-solomon@users.noreply.github.com> * Update docs/management/connectors/action-types/opsgenie.asciidoc Co-authored-by: nastasha-solomon <79124755+nastasha-solomon@users.noreply.github.com> * Addressing feedback * Adding new image with lowercase tags * Addressing feedback * Making executionMode optional * [CI] Auto-commit changed files from 'node scripts/generate codeowners' Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> Co-authored-by: Tyler Smalley <tyler.smalley@elastic.co> Co-authored-by: nastasha-solomon <79124755+nastasha-solomon@users.noreply.github.com>	2022-11-07 11:22:43 -05:00
Tiago Costa	68f82ced36	skip flaky suite (#142715)	2022-11-07 14:46:24 +00:00