-
Notifications
You must be signed in to change notification settings - Fork 8.3k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[RAM] Add window maintenance column to rule logs and rule tables (#15…
…5333) ## Summary Resolves: #153775 This PR adds the `maintenance_window_id` column to the following tables: ## O11Y/Security solutions Alerts table  ## Rule details alerts table  ## Rule run event log  ## To test: 1. Set `ENABLE_MAINTENANCE_WINDOWS` to true in `x-pack/plugins/alerting/public/plugin.ts` 2. Create 1 or more active maintenance windows in stack management 3. Create a rule, trigger some alerts 4. Go to the rule details page alerts table, assert the `maintenance window` column is there, and renders the maintenance window ids 5. Go to the rule details page event log table, assert the `maintenance window` column can enabled, and renders the maintenance window ids 6. Create a O11Y rule, trigger some alerts 7. Go to the O11Y alerts table, assert that the `maintenance_window_id` field can be enabled, and renders the maintenance window ids ### 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: Lisa Cawley <lcawley@elastic.co> Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
- Loading branch information
1 parent
9b6c6bc
commit 9bb127f
Showing
22 changed files
with
307 additions
and
30 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
Oops, something went wrong.