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

Limit rule type creation via HTTP APIs per project #160339

Open
kobelb opened this issue Jun 22, 2023 · 1 comment
Open

Limit rule type creation via HTTP APIs per project #160339

kobelb opened this issue Jun 22, 2023 · 1 comment
Assignees
@XavierM
Labels
Feature:Alerting/RulesManagement Issues related to the Rules Management UX Project:Serverless MVP response-ops-mx-backlog ResponseOps MX backlog Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)

Comments

@kobelb
Copy link
Contributor

kobelb commented Jun 22, 2023 •
edited
Loading

Feature Description

Different Serverless projects will support different alerting rules. In addition to the UIs only displaying the relevant alerting rules, the HTTP APIs should prevent unsupported alerting rules from being created.
Serverless project alerting rule types lists which alerting rules should be available in which serverless projects.

Definition of Done

  • Subset of alerting rules can only be created using the HTTP API for Serverless projects
  • Serverless e2e test verify only the appropriate alerting rules can be created
@kobelb kobelb added Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) Feature:Alerting/RulesManagement Issues related to the Rules Management UX Project:Serverless MVP labels Jun 22, 2023
@elasticmachine
Copy link
Contributor

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

@XavierM XavierM assigned guskovaue and XavierM and unassigned guskovaue Sep 27, 2023
@cnasikas cnasikas added response-ops-mx-backlog ResponseOps MX backlog and removed Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) labels Oct 29, 2024
@botelastic botelastic bot added the needs-team Issues missing a team label label Oct 29, 2024
@wayneseymour wayneseymour added the Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) label Nov 4, 2024
@botelastic botelastic bot removed the needs-team Issues missing a team label label Nov 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@XavierM XavierM

Labels
Feature:Alerting/RulesManagement Issues related to the Rules Management UX Project:Serverless MVP response-ops-mx-backlog ResponseOps MX backlog Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@XavierM @kobelb @wayneseymour @cnasikas @elasticmachine @guskovaue