[Watcher] Revert back to using .watches system index#223898
Merged
ElenaStoeva merged 4 commits intoelastic:mainfrom Jun 16, 2025
Merged
[Watcher] Revert back to using .watches system index#223898ElenaStoeva merged 4 commits intoelastic:mainfrom
ElenaStoeva merged 4 commits intoelastic:mainfrom
Conversation
This reverts commit d9c4817.
ElenaStoeva
added
release_note:fix
Feature:Watcher
Team:Kibana Management
Contributor
|
Pinging @elastic/kibana-management (Team:Kibana Management) |
sabarasaba
reviewed
Jun 16, 2025
Member
sabarasaba
left a comment
sabarasaba
left a comment
There was a problem hiding this comment.
code changes lgtm, tested locally
sabarasaba
approved these changes
Jun 16, 2025
Contributor
💚 Build Succeeded
Metrics [docs]Async chunks
History
cc @ElenaStoeva |
Contributor
|
Starting backport for target branches: 8.18, 8.19, 9.0 |
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Jun 16, 2025
Fixes elastic#221820 Fixes elastic#220879 ## Summary This PR reverts elastic#204296 and elastic#218853 as these PRs caused issues in the UI due to limitations in the Query Watches API. Therefore, we are temporarily reverting back to fetching watches through the `.watches` system index until we have better support from the Query Watches API. **How to test:** 1. Start Es with `yarn es snapshot --license=trial` and Kibana with `yarn start` (no need to test in serverless as Watcher is not available there. 2. Navigate to Stack Management -> Watcher and create multiple watches (the more, the better). Make sure you create watches of different types (advanced/json or threshold), watches with or without names, etc. There are different watches and use cases described in the [documentation](https://www.elastic.co/docs/explore-analyze/alerts-cases/watcher). Also, adding sample data sets is helpful so that you can get watches to execute and have values under the "Condition last met" and "Last checked" columns. 3. After creating various watches, open the table with watches and make sure that all functionalities work correctly. For example: - All watches are displayed, check with >10 watches and different page sizes. - Sorting works for all columns. - Search bar works as expected and searching by partial id is supported. - Deleting watches updates the table correctly. https://github.com/user-attachments/assets/d0da9c24-7389-481d-8a16-a0d01bda0e80 ## Release notes: This update resolves multiple issues in Watcher UI that were introduced in 8.18.0, 8.18.1, 9.0.0, and 9.1.0, including the table not displaying more than 10 watches, an error banner appearing unexpectedly in certain scenarios, and the search bar functionality not working as expected. (cherry picked from commit 5c0b6b0)
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Jun 16, 2025
Fixes elastic#221820 Fixes elastic#220879 ## Summary This PR reverts elastic#204296 and elastic#218853 as these PRs caused issues in the UI due to limitations in the Query Watches API. Therefore, we are temporarily reverting back to fetching watches through the `.watches` system index until we have better support from the Query Watches API. **How to test:** 1. Start Es with `yarn es snapshot --license=trial` and Kibana with `yarn start` (no need to test in serverless as Watcher is not available there. 2. Navigate to Stack Management -> Watcher and create multiple watches (the more, the better). Make sure you create watches of different types (advanced/json or threshold), watches with or without names, etc. There are different watches and use cases described in the [documentation](https://www.elastic.co/docs/explore-analyze/alerts-cases/watcher). Also, adding sample data sets is helpful so that you can get watches to execute and have values under the "Condition last met" and "Last checked" columns. 3. After creating various watches, open the table with watches and make sure that all functionalities work correctly. For example: - All watches are displayed, check with >10 watches and different page sizes. - Sorting works for all columns. - Search bar works as expected and searching by partial id is supported. - Deleting watches updates the table correctly. https://github.com/user-attachments/assets/d0da9c24-7389-481d-8a16-a0d01bda0e80 ## Release notes: This update resolves multiple issues in Watcher UI that were introduced in 8.18.0, 8.18.1, 9.0.0, and 9.1.0, including the table not displaying more than 10 watches, an error banner appearing unexpectedly in certain scenarios, and the search bar functionality not working as expected. (cherry picked from commit 5c0b6b0)
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Jun 16, 2025
Fixes elastic#221820 Fixes elastic#220879 ## Summary This PR reverts elastic#204296 and elastic#218853 as these PRs caused issues in the UI due to limitations in the Query Watches API. Therefore, we are temporarily reverting back to fetching watches through the `.watches` system index until we have better support from the Query Watches API. **How to test:** 1. Start Es with `yarn es snapshot --license=trial` and Kibana with `yarn start` (no need to test in serverless as Watcher is not available there. 2. Navigate to Stack Management -> Watcher and create multiple watches (the more, the better). Make sure you create watches of different types (advanced/json or threshold), watches with or without names, etc. There are different watches and use cases described in the [documentation](https://www.elastic.co/docs/explore-analyze/alerts-cases/watcher). Also, adding sample data sets is helpful so that you can get watches to execute and have values under the "Condition last met" and "Last checked" columns. 3. After creating various watches, open the table with watches and make sure that all functionalities work correctly. For example: - All watches are displayed, check with >10 watches and different page sizes. - Sorting works for all columns. - Search bar works as expected and searching by partial id is supported. - Deleting watches updates the table correctly. https://github.com/user-attachments/assets/d0da9c24-7389-481d-8a16-a0d01bda0e80 ## Release notes: This update resolves multiple issues in Watcher UI that were introduced in 8.18.0, 8.18.1, 9.0.0, and 9.1.0, including the table not displaying more than 10 watches, an error banner appearing unexpectedly in certain scenarios, and the search bar functionality not working as expected. (cherry picked from commit 5c0b6b0)
Contributor
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
kibanamachine
added a commit
that referenced
this pull request
Jun 16, 2025
…224080) # Backport This will backport the following commits from `main` to `9.0`: - [[Watcher] Revert back to using .watches system index (#223898)](#223898) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Elena Stoeva","email":"59341489+ElenaStoeva@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-06-16T14:26:24Z","message":"[Watcher] Revert back to using .watches system index (#223898)\n\nFixes https://github.com/elastic/kibana/issues/221820\nFixes https://github.com/elastic/kibana/issues/220879\n\n## Summary\n\nThis PR reverts #204296 and\nhttps://github.com//pull/218853 as these PRs caused issues\nin the UI due to limitations in the Query Watches API. Therefore, we are\ntemporarily reverting back to fetching watches through the `.watches`\nsystem index until we have better support from the Query Watches API.\n\n**How to test:**\n1. Start Es with `yarn es snapshot --license=trial` and Kibana with\n`yarn start` (no need to test in serverless as Watcher is not available\nthere.\n2. Navigate to Stack Management -> Watcher and create multiple watches\n(the more, the better). Make sure you create watches of different types\n(advanced/json or threshold), watches with or without names, etc. There\nare different watches and use cases described in the\n[documentation](https://www.elastic.co/docs/explore-analyze/alerts-cases/watcher).\nAlso, adding sample data sets is helpful so that you can get watches to\nexecute and have values under the \"Condition last met\" and \"Last\nchecked\" columns.\n3. After creating various watches, open the table with watches and make\nsure that all functionalities work correctly. For example:\n- All watches are displayed, check with >10 watches and different page\nsizes.\n- Sorting works for all columns.\n- Search bar works as expected and searching by partial id is supported.\n- Deleting watches updates the table correctly.\n\n\nhttps://github.com/user-attachments/assets/d0da9c24-7389-481d-8a16-a0d01bda0e80\n\n## Release notes:\nThis update resolves multiple issues in Watcher UI that were introduced\nin 8.18.0, 8.18.1, 9.0.0, and 9.1.0, including the table not displaying\nmore than 10 watches, an error banner appearing unexpectedly in certain\nscenarios, and the search bar functionality not working as expected.","sha":"5c0b6b0fe7c08b20a6cc540b0e90b8106147b54a","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Feature:Watcher","Team:Kibana Management","backport:version","v9.1.0","v8.19.0","v9.0.3","v8.18.3"],"title":"[Watcher] Revert back to using .watches system index","number":223898,"url":"https://github.com/elastic/kibana/pull/223898","mergeCommit":{"message":"[Watcher] Revert back to using .watches system index (#223898)\n\nFixes https://github.com/elastic/kibana/issues/221820\nFixes https://github.com/elastic/kibana/issues/220879\n\n## Summary\n\nThis PR reverts #204296 and\nhttps://github.com//pull/218853 as these PRs caused issues\nin the UI due to limitations in the Query Watches API. Therefore, we are\ntemporarily reverting back to fetching watches through the `.watches`\nsystem index until we have better support from the Query Watches API.\n\n**How to test:**\n1. Start Es with `yarn es snapshot --license=trial` and Kibana with\n`yarn start` (no need to test in serverless as Watcher is not available\nthere.\n2. Navigate to Stack Management -> Watcher and create multiple watches\n(the more, the better). Make sure you create watches of different types\n(advanced/json or threshold), watches with or without names, etc. There\nare different watches and use cases described in the\n[documentation](https://www.elastic.co/docs/explore-analyze/alerts-cases/watcher).\nAlso, adding sample data sets is helpful so that you can get watches to\nexecute and have values under the \"Condition last met\" and \"Last\nchecked\" columns.\n3. After creating various watches, open the table with watches and make\nsure that all functionalities work correctly. For example:\n- All watches are displayed, check with >10 watches and different page\nsizes.\n- Sorting works for all columns.\n- Search bar works as expected and searching by partial id is supported.\n- Deleting watches updates the table correctly.\n\n\nhttps://github.com/user-attachments/assets/d0da9c24-7389-481d-8a16-a0d01bda0e80\n\n## Release notes:\nThis update resolves multiple issues in Watcher UI that were introduced\nin 8.18.0, 8.18.1, 9.0.0, and 9.1.0, including the table not displaying\nmore than 10 watches, an error banner appearing unexpectedly in certain\nscenarios, and the search bar functionality not working as expected.","sha":"5c0b6b0fe7c08b20a6cc540b0e90b8106147b54a"}},"sourceBranch":"main","suggestedTargetBranches":["8.19","9.0","8.18"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/223898","number":223898,"mergeCommit":{"message":"[Watcher] Revert back to using .watches system index (#223898)\n\nFixes https://github.com/elastic/kibana/issues/221820\nFixes https://github.com/elastic/kibana/issues/220879\n\n## Summary\n\nThis PR reverts #204296 and\nhttps://github.com//pull/218853 as these PRs caused issues\nin the UI due to limitations in the Query Watches API. Therefore, we are\ntemporarily reverting back to fetching watches through the `.watches`\nsystem index until we have better support from the Query Watches API.\n\n**How to test:**\n1. Start Es with `yarn es snapshot --license=trial` and Kibana with\n`yarn start` (no need to test in serverless as Watcher is not available\nthere.\n2. Navigate to Stack Management -> Watcher and create multiple watches\n(the more, the better). Make sure you create watches of different types\n(advanced/json or threshold), watches with or without names, etc. There\nare different watches and use cases described in the\n[documentation](https://www.elastic.co/docs/explore-analyze/alerts-cases/watcher).\nAlso, adding sample data sets is helpful so that you can get watches to\nexecute and have values under the \"Condition last met\" and \"Last\nchecked\" columns.\n3. After creating various watches, open the table with watches and make\nsure that all functionalities work correctly. For example:\n- All watches are displayed, check with >10 watches and different page\nsizes.\n- Sorting works for all columns.\n- Search bar works as expected and searching by partial id is supported.\n- Deleting watches updates the table correctly.\n\n\nhttps://github.com/user-attachments/assets/d0da9c24-7389-481d-8a16-a0d01bda0e80\n\n## Release notes:\nThis update resolves multiple issues in Watcher UI that were introduced\nin 8.18.0, 8.18.1, 9.0.0, and 9.1.0, including the table not displaying\nmore than 10 watches, an error banner appearing unexpectedly in certain\nscenarios, and the search bar functionality not working as expected.","sha":"5c0b6b0fe7c08b20a6cc540b0e90b8106147b54a"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Elena Stoeva <59341489+ElenaStoeva@users.noreply.github.com>
kibanamachine
added a commit
that referenced
this pull request
Jun 16, 2025
…#224079) # Backport This will backport the following commits from `main` to `8.19`: - [[Watcher] Revert back to using .watches system index (#223898)](#223898) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Elena Stoeva","email":"59341489+ElenaStoeva@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-06-16T14:26:24Z","message":"[Watcher] Revert back to using .watches system index (#223898)\n\nFixes https://github.com/elastic/kibana/issues/221820\nFixes https://github.com/elastic/kibana/issues/220879\n\n## Summary\n\nThis PR reverts #204296 and\nhttps://github.com//pull/218853 as these PRs caused issues\nin the UI due to limitations in the Query Watches API. Therefore, we are\ntemporarily reverting back to fetching watches through the `.watches`\nsystem index until we have better support from the Query Watches API.\n\n**How to test:**\n1. Start Es with `yarn es snapshot --license=trial` and Kibana with\n`yarn start` (no need to test in serverless as Watcher is not available\nthere.\n2. Navigate to Stack Management -> Watcher and create multiple watches\n(the more, the better). Make sure you create watches of different types\n(advanced/json or threshold), watches with or without names, etc. There\nare different watches and use cases described in the\n[documentation](https://www.elastic.co/docs/explore-analyze/alerts-cases/watcher).\nAlso, adding sample data sets is helpful so that you can get watches to\nexecute and have values under the \"Condition last met\" and \"Last\nchecked\" columns.\n3. After creating various watches, open the table with watches and make\nsure that all functionalities work correctly. For example:\n- All watches are displayed, check with >10 watches and different page\nsizes.\n- Sorting works for all columns.\n- Search bar works as expected and searching by partial id is supported.\n- Deleting watches updates the table correctly.\n\n\nhttps://github.com/user-attachments/assets/d0da9c24-7389-481d-8a16-a0d01bda0e80\n\n## Release notes:\nThis update resolves multiple issues in Watcher UI that were introduced\nin 8.18.0, 8.18.1, 9.0.0, and 9.1.0, including the table not displaying\nmore than 10 watches, an error banner appearing unexpectedly in certain\nscenarios, and the search bar functionality not working as expected.","sha":"5c0b6b0fe7c08b20a6cc540b0e90b8106147b54a","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Feature:Watcher","Team:Kibana Management","backport:version","v9.1.0","v8.19.0","v9.0.3","v8.18.3"],"title":"[Watcher] Revert back to using .watches system index","number":223898,"url":"https://github.com/elastic/kibana/pull/223898","mergeCommit":{"message":"[Watcher] Revert back to using .watches system index (#223898)\n\nFixes https://github.com/elastic/kibana/issues/221820\nFixes https://github.com/elastic/kibana/issues/220879\n\n## Summary\n\nThis PR reverts #204296 and\nhttps://github.com//pull/218853 as these PRs caused issues\nin the UI due to limitations in the Query Watches API. Therefore, we are\ntemporarily reverting back to fetching watches through the `.watches`\nsystem index until we have better support from the Query Watches API.\n\n**How to test:**\n1. Start Es with `yarn es snapshot --license=trial` and Kibana with\n`yarn start` (no need to test in serverless as Watcher is not available\nthere.\n2. Navigate to Stack Management -> Watcher and create multiple watches\n(the more, the better). Make sure you create watches of different types\n(advanced/json or threshold), watches with or without names, etc. There\nare different watches and use cases described in the\n[documentation](https://www.elastic.co/docs/explore-analyze/alerts-cases/watcher).\nAlso, adding sample data sets is helpful so that you can get watches to\nexecute and have values under the \"Condition last met\" and \"Last\nchecked\" columns.\n3. After creating various watches, open the table with watches and make\nsure that all functionalities work correctly. For example:\n- All watches are displayed, check with >10 watches and different page\nsizes.\n- Sorting works for all columns.\n- Search bar works as expected and searching by partial id is supported.\n- Deleting watches updates the table correctly.\n\n\nhttps://github.com/user-attachments/assets/d0da9c24-7389-481d-8a16-a0d01bda0e80\n\n## Release notes:\nThis update resolves multiple issues in Watcher UI that were introduced\nin 8.18.0, 8.18.1, 9.0.0, and 9.1.0, including the table not displaying\nmore than 10 watches, an error banner appearing unexpectedly in certain\nscenarios, and the search bar functionality not working as expected.","sha":"5c0b6b0fe7c08b20a6cc540b0e90b8106147b54a"}},"sourceBranch":"main","suggestedTargetBranches":["8.19","9.0","8.18"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/223898","number":223898,"mergeCommit":{"message":"[Watcher] Revert back to using .watches system index (#223898)\n\nFixes https://github.com/elastic/kibana/issues/221820\nFixes https://github.com/elastic/kibana/issues/220879\n\n## Summary\n\nThis PR reverts #204296 and\nhttps://github.com//pull/218853 as these PRs caused issues\nin the UI due to limitations in the Query Watches API. Therefore, we are\ntemporarily reverting back to fetching watches through the `.watches`\nsystem index until we have better support from the Query Watches API.\n\n**How to test:**\n1. Start Es with `yarn es snapshot --license=trial` and Kibana with\n`yarn start` (no need to test in serverless as Watcher is not available\nthere.\n2. Navigate to Stack Management -> Watcher and create multiple watches\n(the more, the better). Make sure you create watches of different types\n(advanced/json or threshold), watches with or without names, etc. There\nare different watches and use cases described in the\n[documentation](https://www.elastic.co/docs/explore-analyze/alerts-cases/watcher).\nAlso, adding sample data sets is helpful so that you can get watches to\nexecute and have values under the \"Condition last met\" and \"Last\nchecked\" columns.\n3. After creating various watches, open the table with watches and make\nsure that all functionalities work correctly. For example:\n- All watches are displayed, check with >10 watches and different page\nsizes.\n- Sorting works for all columns.\n- Search bar works as expected and searching by partial id is supported.\n- Deleting watches updates the table correctly.\n\n\nhttps://github.com/user-attachments/assets/d0da9c24-7389-481d-8a16-a0d01bda0e80\n\n## Release notes:\nThis update resolves multiple issues in Watcher UI that were introduced\nin 8.18.0, 8.18.1, 9.0.0, and 9.1.0, including the table not displaying\nmore than 10 watches, an error banner appearing unexpectedly in certain\nscenarios, and the search bar functionality not working as expected.","sha":"5c0b6b0fe7c08b20a6cc540b0e90b8106147b54a"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Elena Stoeva <59341489+ElenaStoeva@users.noreply.github.com>
kibanamachine
added a commit
that referenced
this pull request
Jun 16, 2025
…#224078) # Backport This will backport the following commits from `main` to `8.18`: - [[Watcher] Revert back to using .watches system index (#223898)](#223898) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Elena Stoeva","email":"59341489+ElenaStoeva@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-06-16T14:26:24Z","message":"[Watcher] Revert back to using .watches system index (#223898)\n\nFixes https://github.com/elastic/kibana/issues/221820\nFixes https://github.com/elastic/kibana/issues/220879\n\n## Summary\n\nThis PR reverts #204296 and\nhttps://github.com//pull/218853 as these PRs caused issues\nin the UI due to limitations in the Query Watches API. Therefore, we are\ntemporarily reverting back to fetching watches through the `.watches`\nsystem index until we have better support from the Query Watches API.\n\n**How to test:**\n1. Start Es with `yarn es snapshot --license=trial` and Kibana with\n`yarn start` (no need to test in serverless as Watcher is not available\nthere.\n2. Navigate to Stack Management -> Watcher and create multiple watches\n(the more, the better). Make sure you create watches of different types\n(advanced/json or threshold), watches with or without names, etc. There\nare different watches and use cases described in the\n[documentation](https://www.elastic.co/docs/explore-analyze/alerts-cases/watcher).\nAlso, adding sample data sets is helpful so that you can get watches to\nexecute and have values under the \"Condition last met\" and \"Last\nchecked\" columns.\n3. After creating various watches, open the table with watches and make\nsure that all functionalities work correctly. For example:\n- All watches are displayed, check with >10 watches and different page\nsizes.\n- Sorting works for all columns.\n- Search bar works as expected and searching by partial id is supported.\n- Deleting watches updates the table correctly.\n\n\nhttps://github.com/user-attachments/assets/d0da9c24-7389-481d-8a16-a0d01bda0e80\n\n## Release notes:\nThis update resolves multiple issues in Watcher UI that were introduced\nin 8.18.0, 8.18.1, 9.0.0, and 9.1.0, including the table not displaying\nmore than 10 watches, an error banner appearing unexpectedly in certain\nscenarios, and the search bar functionality not working as expected.","sha":"5c0b6b0fe7c08b20a6cc540b0e90b8106147b54a","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Feature:Watcher","Team:Kibana Management","backport:version","v9.1.0","v8.19.0","v9.0.3","v8.18.3"],"title":"[Watcher] Revert back to using .watches system index","number":223898,"url":"https://github.com/elastic/kibana/pull/223898","mergeCommit":{"message":"[Watcher] Revert back to using .watches system index (#223898)\n\nFixes https://github.com/elastic/kibana/issues/221820\nFixes https://github.com/elastic/kibana/issues/220879\n\n## Summary\n\nThis PR reverts #204296 and\nhttps://github.com//pull/218853 as these PRs caused issues\nin the UI due to limitations in the Query Watches API. Therefore, we are\ntemporarily reverting back to fetching watches through the `.watches`\nsystem index until we have better support from the Query Watches API.\n\n**How to test:**\n1. Start Es with `yarn es snapshot --license=trial` and Kibana with\n`yarn start` (no need to test in serverless as Watcher is not available\nthere.\n2. Navigate to Stack Management -> Watcher and create multiple watches\n(the more, the better). Make sure you create watches of different types\n(advanced/json or threshold), watches with or without names, etc. There\nare different watches and use cases described in the\n[documentation](https://www.elastic.co/docs/explore-analyze/alerts-cases/watcher).\nAlso, adding sample data sets is helpful so that you can get watches to\nexecute and have values under the \"Condition last met\" and \"Last\nchecked\" columns.\n3. After creating various watches, open the table with watches and make\nsure that all functionalities work correctly. For example:\n- All watches are displayed, check with >10 watches and different page\nsizes.\n- Sorting works for all columns.\n- Search bar works as expected and searching by partial id is supported.\n- Deleting watches updates the table correctly.\n\n\nhttps://github.com/user-attachments/assets/d0da9c24-7389-481d-8a16-a0d01bda0e80\n\n## Release notes:\nThis update resolves multiple issues in Watcher UI that were introduced\nin 8.18.0, 8.18.1, 9.0.0, and 9.1.0, including the table not displaying\nmore than 10 watches, an error banner appearing unexpectedly in certain\nscenarios, and the search bar functionality not working as expected.","sha":"5c0b6b0fe7c08b20a6cc540b0e90b8106147b54a"}},"sourceBranch":"main","suggestedTargetBranches":["8.19","9.0","8.18"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/223898","number":223898,"mergeCommit":{"message":"[Watcher] Revert back to using .watches system index (#223898)\n\nFixes https://github.com/elastic/kibana/issues/221820\nFixes https://github.com/elastic/kibana/issues/220879\n\n## Summary\n\nThis PR reverts #204296 and\nhttps://github.com//pull/218853 as these PRs caused issues\nin the UI due to limitations in the Query Watches API. Therefore, we are\ntemporarily reverting back to fetching watches through the `.watches`\nsystem index until we have better support from the Query Watches API.\n\n**How to test:**\n1. Start Es with `yarn es snapshot --license=trial` and Kibana with\n`yarn start` (no need to test in serverless as Watcher is not available\nthere.\n2. Navigate to Stack Management -> Watcher and create multiple watches\n(the more, the better). Make sure you create watches of different types\n(advanced/json or threshold), watches with or without names, etc. There\nare different watches and use cases described in the\n[documentation](https://www.elastic.co/docs/explore-analyze/alerts-cases/watcher).\nAlso, adding sample data sets is helpful so that you can get watches to\nexecute and have values under the \"Condition last met\" and \"Last\nchecked\" columns.\n3. After creating various watches, open the table with watches and make\nsure that all functionalities work correctly. For example:\n- All watches are displayed, check with >10 watches and different page\nsizes.\n- Sorting works for all columns.\n- Search bar works as expected and searching by partial id is supported.\n- Deleting watches updates the table correctly.\n\n\nhttps://github.com/user-attachments/assets/d0da9c24-7389-481d-8a16-a0d01bda0e80\n\n## Release notes:\nThis update resolves multiple issues in Watcher UI that were introduced\nin 8.18.0, 8.18.1, 9.0.0, and 9.1.0, including the table not displaying\nmore than 10 watches, an error banner appearing unexpectedly in certain\nscenarios, and the search bar functionality not working as expected.","sha":"5c0b6b0fe7c08b20a6cc540b0e90b8106147b54a"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Elena Stoeva <59341489+ElenaStoeva@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #221820
Fixes #220879
Summary
This PR reverts #204296 and #218853 as these PRs caused issues in the UI due to limitations in the Query Watches API. Therefore, we are temporarily reverting back to fetching watches through the
.watchessystem index until we have better support from the Query Watches API.How to test:
yarn es snapshot --license=trialand Kibana withyarn start(no need to test in serverless as Watcher is not available there.watcher.mov
Release notes:
This update resolves multiple issues in Watcher UI that were introduced in 8.18.0, 8.18.1, 9.0.0, and 9.1.0, including the table not displaying more than 10 watches, an error banner appearing unexpectedly in certain scenarios, and the search bar functionality not working as expected.