-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Cannot delete rules or connectors in SO Management #107421
Comments
I recall a discussion around deletion in the early discussion of leveraging SO management for alerting import/export. I will defer to @elastic/kibana-core for advice on how to handle the UX for deletion of hidden SO types. From alerting perspective, there are some workflows we would prefer to run (by going through alerting HTTP APIs) but could explore alternate options. Regarding the filtering, @arisonl opened an issue here: #105575. |
Pinging @elastic/kibana-alerting-services (Team:Alerting Services) |
I believe there was some discussion about allowing deletion of |
Reading the comment @ymao1 has linked to it sounds like this is something that needs to be done in SOM right? Rather than Alerting code. |
Forwarding this issue to @elastic/kibana-core team |
I'll go ahead and close this as a duplicate of #106581, where we are discussing how to improve the UX for deleting hidden SOs. @alexfrancoeur feel free to re-open if there's something which isn't captured in that issue |
In testing out some of the new import / export functionality in 7.14 (#50266) I discovered that I am not able to delete rules or connectors from the SO management UI. Is this expected behavior?
The connector is pagerduty and the rule is a logs threshold rule. Export from one environment and imported into another worked flawlessly.
Unrelated (at least, I think it is), I see filters for the old terminology of SO's. Actions & alerts. Is this something we plan to resolve with the terminology switch / migration?
cc: @mikecote @gmmorris @arisonl
The text was updated successfully, but these errors were encountered: