[RAM] Maintenance window - Expose endpoint to return active maintenance windows #155306
Assignees
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
|
Pinging @elastic/response-ops (Team:ResponseOps) |
1 task
JiaweiWu
added a commit
that referenced
this issue
Apr 20, 2023
…55321) ## Summary Resolves: #155306 Exposes the `/_active` route to get all currently active maintenance windows ``` GET `${INTERNAL_BASE_ALERTING_API_PATH}/rules/maintenance_window/_active` body: {} Response: MaintenanceWindow[] ``` ### Checklist Delete any items that are not applicable to this PR. - [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
nikitaindik
pushed a commit
to nikitaindik/kibana
that referenced
this issue
Apr 25, 2023
…astic#155321) ## Summary Resolves: elastic#155306 Exposes the `/_active` route to get all currently active maintenance windows ``` GET `${INTERNAL_BASE_ALERTING_API_PATH}/rules/maintenance_window/_active` body: {} Response: MaintenanceWindow[] ``` ### Checklist Delete any items that are not applicable to this PR. - [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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Parent issue: #152032
We want to create a new
/_activeendpoint that returns all of the active maintenance windows currently.The text was updated successfully, but these errors were encountered: