Skip to content
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

[Response Ops][Alerting] Implement alert deletion UI #208621

Open
ymao1 opened this issue Jan 28, 2025 · 1 comment
Open

[Response Ops][Alerting] Implement alert deletion UI #208621

ymao1 opened this issue Jan 28, 2025 · 1 comment
Labels
Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)

Comments

@ymao1
Copy link
Contributor

ymao1 commented Jan 28, 2025

Blocked by #208615

We would like to allow users the ability to delete their alerts based on certain configuration conditions. This issue covers the UI changes required for the alert deletion MVP and would use the API from #208615

  • This UI should appear on the Stack Management > Rules page under the existing Settings option
  • This UI should allow users to enable/disable 2 conditions
    1. delete active alerts created more than N days ago (where N is configurable by the user)
    2. delete inactive alerts that were recovered/closed/untracked more than N days ago (where N is configurable by the user)
  • By default, the configuration should show "Delete inactive alerts were recovered, closed or untracked more than 90 days ago"
  • This UI should allow users to select whether the setting applies to Observability/Stack/Security alerts (can select 1+)
  • This UI should call the "last run" API from [Response Ops][Alerting] Implement alert deletion task #208615 to show the last time the task was run
  • As the user changes the configuration, the UI should call the preview API from [Response Ops][Alerting] Implement alert deletion task #208615 to show the number of alerts that would be deleted with the current configuration
  • If the user changes the rules setting configuration, the UI should show a "Save and Run" button that saves the changes and schedules the task. If the user does not change the configuration, the UI should show a "Run" button that schedules the task
  • The UI should be a reusable component that Security Solutions can show in their UI. If it's shown in their UI, the option for Observability/Stack/Security should not be shown, instead it should auto-select Security.
@ymao1 ymao1 added Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) labels Jan 28, 2025
@elasticmachine
Copy link
Contributor

Pinging @elastic/response-ops (Team:ResponseOps)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)
Projects
None yet
Development

No branches or pull requests

2 participants
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy