-
Notifications
You must be signed in to change notification settings - Fork 8.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[RAM] Window Maintenance - Create alerting client and saved object mapping #152270
Labels
Feature:Alerting/RulesManagement
Issues related to the Rules Management UX
Team:ResponseOps
Label for the ResponseOps team (formerly the Cases and Alerting teams)
v8.8.0
Comments
JiaweiWu
added
Team:ResponseOps
Label for the ResponseOps team (formerly the Cases and Alerting teams)
Feature:Alerting/RulesManagement
Issues related to the Rules Management UX
v8.8.0
labels
Feb 27, 2023
Pinging @elastic/response-ops (Team:ResponseOps) |
JiaweiWu
added a commit
that referenced
this issue
Apr 13, 2023
…153411) ## Summary Resolves: #152270 Specs: https://docs.google.com/document/u/1/d/1-QblF6P19W9o5-10Us3bfgN80GRfjSIhybHrvJS_ObA/edit This PR implements the following: - New maintenance window SO - New maintenance window client in the alerting plugin (generates and queries maintenance window events, and other CRUD functionality around the SO) - New maintenance window REST APIs - Kibana privileges for reading/writing maintenance window This PR does not include integration with task runner, a new PR will be created to do that work. ## APIs: ``` Find all maintenance windows in current space GET `${INTERNAL_BASE_ALERTING_API_PATH}/rules/maintenance_window/_find` body: {} ``` ``` Create maintenance window: POST `${INTERNAL_BASE_ALERTING_API_PATH}/rules/maintenance_window` body: { title: string, duration: number, r_rule: RRule } ``` ``` Update maintenance window by ID: POST `${INTERNAL_BASE_ALERTING_API_PATH}/rules/maintenance_window/{id}`, body: { title?: string, duration?: number, enabled?: boolean, r_rule?: RRule, } ``` ``` Get maintenance window by ID: GET `${INTERNAL_BASE_ALERTING_API_PATH}/rules/maintenance_window/{id}`, ``` ``` Delete maintenance window by ID: DELETE `${INTERNAL_BASE_ALERTING_API_PATH}/rules/maintenance_window/{id}`, ``` ``` Archive maintenance window by ID: POST `${INTERNAL_BASE_ALERTING_API_PATH}/rules/maintenance_window/{id}/_archive`, body: { archive: boolean } ``` ``` Finish maintenance window by ID: POST `${INTERNAL_BASE_ALERTING_API_PATH}/rules/maintenance_window/{id}/_finish`, ``` ## Maintenance window response schema: ``` { id: string; title: string; enabled: boolean; duration: number; expirationDate: string; events: DateRange[]; rRule: RRuleParams; status: 'running' | 'upcoming' | 'finished' | 'archived'; startDate: string | null; endDate: string | null; createdBy: string | null; updatedBy: string | null; createdAt: string; updatedAt: string; } ``` --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
saarikabhasi
pushed a commit
to saarikabhasi/kibana
that referenced
this issue
Apr 19, 2023
…lastic#153411) ## Summary Resolves: elastic#152270 Specs: https://docs.google.com/document/u/1/d/1-QblF6P19W9o5-10Us3bfgN80GRfjSIhybHrvJS_ObA/edit This PR implements the following: - New maintenance window SO - New maintenance window client in the alerting plugin (generates and queries maintenance window events, and other CRUD functionality around the SO) - New maintenance window REST APIs - Kibana privileges for reading/writing maintenance window This PR does not include integration with task runner, a new PR will be created to do that work. ## APIs: ``` Find all maintenance windows in current space GET `${INTERNAL_BASE_ALERTING_API_PATH}/rules/maintenance_window/_find` body: {} ``` ``` Create maintenance window: POST `${INTERNAL_BASE_ALERTING_API_PATH}/rules/maintenance_window` body: { title: string, duration: number, r_rule: RRule } ``` ``` Update maintenance window by ID: POST `${INTERNAL_BASE_ALERTING_API_PATH}/rules/maintenance_window/{id}`, body: { title?: string, duration?: number, enabled?: boolean, r_rule?: RRule, } ``` ``` Get maintenance window by ID: GET `${INTERNAL_BASE_ALERTING_API_PATH}/rules/maintenance_window/{id}`, ``` ``` Delete maintenance window by ID: DELETE `${INTERNAL_BASE_ALERTING_API_PATH}/rules/maintenance_window/{id}`, ``` ``` Archive maintenance window by ID: POST `${INTERNAL_BASE_ALERTING_API_PATH}/rules/maintenance_window/{id}/_archive`, body: { archive: boolean } ``` ``` Finish maintenance window by ID: POST `${INTERNAL_BASE_ALERTING_API_PATH}/rules/maintenance_window/{id}/_finish`, ``` ## Maintenance window response schema: ``` { id: string; title: string; enabled: boolean; duration: number; expirationDate: string; events: DateRange[]; rRule: RRuleParams; status: 'running' | 'upcoming' | 'finished' | 'archived'; startDate: string | null; endDate: string | null; createdBy: string | null; updatedBy: string | null; createdAt: string; updatedAt: string; } ``` --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Feature:Alerting/RulesManagement
Issues related to the Rules Management UX
Team:ResponseOps
Label for the ResponseOps team (formerly the Cases and Alerting teams)
v8.8.0
Parent issue: #152032
Create the alerting client (similar to how flapping settings were done) and the saved object mapping for window maintenance.
The text was updated successfully, but these errors were encountered: