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.

Sign up for GitHub

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

Jump to bottom

Rename alerting SO types to reflect new terminology #100068

Open
mikecote opened this issue May 13, 2021 · 4 comments
Open

Rename alerting SO types to reflect new terminology #100068

mikecote opened this issue May 13, 2021 · 4 comments
Labels
estimate:needs-research Estimated as too large and requires research to break down into workable issues Feature:Actions/Framework Issues related to the Actions Framework Feature:Actions Feature:Alerting/RulesFramework Issues related to the Alerting Rules Framework Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) technical debt Improvement of the software architecture and operational architecture

Comments

@mikecote
Copy link
Contributor

mikecote commented May 13, 2021 •
edited
Loading

Part of #90375

Once #91143 is resolved, we should rename some of our saved object types to reflect the new terminology.

  • alert -> rule
  • action -> connector

This can be cleaned up when telemetry from #108716 shows usage is below 1% or deprecated for > 2.5 years after deprecating legacy terminology usage.
@mikecote mikecote added Feature:Alerting Feature:Actions Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) labels May 13, 2021
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-alerting-services (Team:Alerting Services)

@mikecote mikecote mentioned this issue May 13, 2021
Open
17 tasks
@gmmorris gmmorris mentioned this issue Jun 9, 2021
Open
@mikecote mikecote changed the title [8.0 only] Rename alerting SO types to reflect new terminology Rename alerting SO types to reflect new terminology Jun 15, 2021
@mikecote
Copy link
Contributor Author

mikecote commented Jun 15, 2021 •
edited
Loading

Removing [8.0 only] from the title as this issue may not be considered a breaking change.

@gmmorris gmmorris added Feature:Actions/Framework Issues related to the Actions Framework Feature:Alerting/RulesFramework Issues related to the Alerting Rules Framework labels Jul 1, 2021
@mikecote mikecote mentioned this issue Jul 5, 2021
Closed
@gmmorris gmmorris added the loe:needs-research This issue requires some research before it can be worked on or estimated label Jul 14, 2021
@ymao1 ymao1 mentioned this issue Jul 21, 2021
Merged
2 tasks
@gmmorris gmmorris added the technical debt Improvement of the software architecture and operational architecture label Aug 13, 2021
@mikecote mikecote mentioned this issue Aug 16, 2021
Closed
@gmmorris gmmorris added the estimate:needs-research Estimated as too large and requires research to break down into workable issues label Aug 18, 2021
@gmmorris gmmorris removed the loe:needs-research This issue requires some research before it can be worked on or estimated label Sep 2, 2021
@kobelb kobelb added the needs-team Issues missing a team label label Jan 31, 2022
@botelastic botelastic bot removed the needs-team Issues missing a team label label Jan 31, 2022
@cnasikas
Copy link
Member

cnasikas commented May 8, 2024

@mikecote Is this still valid with the SO migration restrictions in Serverless?

@mikecote
Copy link
Contributor Author

I don't know if it is still possible but it would be nice to limit the surface as much as possible otherwise.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
estimate:needs-research Estimated as too large and requires research to break down into workable issues Feature:Actions/Framework Issues related to the Actions Framework Feature:Actions Feature:Alerting/RulesFramework Issues related to the Alerting Rules Framework Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) technical debt Improvement of the software architecture and operational architecture
Projects
No open projects
AppEx: ResponseOps - Execution & Connectors
Status: Todo
AppEx: ResponseOps - Rules & Alerts Management
Status: No status
Milestone
No milestone
Development

No branches or pull requests
5 participants
@gmmorris @kobelb @mikecote @cnasikas @elasticmachine