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

Make non-ResponseOps owned rule types flag user errors #180966

Open
24 tasks
mikecote opened this issue Apr 16, 2024 · 1 comment
Open
24 tasks

Make non-ResponseOps owned rule types flag user errors #180966

mikecote opened this issue Apr 16, 2024 · 1 comment
Labels
blocked Feature:Alerting response-ops-ec-backlog ResponseOps E&C backlog Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)

Comments

@mikecote
Copy link
Contributor

Blocked on: #180963

We should reach out to the owning teams of the rule types used in serverless (most listed below) and make them report user errors accordingly. They must follow the guidelines from #180963 to properly flag user type errors.

Rule Types:

  • Transform health
  • Tracking containment
  • Custom threshold
  • SLO burn rate
  • Anomaly detection
  • Anomaly detection jobs health
  • Inventory
  • Latency threshold
  • APM Anomaly
  • Error count threshold
  • Failed transaction rate threshold
  • Event Correlation Rule
  • ES|QL Rule
  • Saved Query Rule
  • Indicator Match Rule
  • Machine Learning Rule
  • Custom Query Rule
  • Threshold Rule
  • New Terms Rule
  • Security Solution notification (Legacy)
  • ... see if there are more (serverless only) ...

Definition of Done

  • All owning teams have GitHub issues requesting them to flag user type errors accordingly
  • GitHub issues reference our guidelines
  • Checked to see if there are more rule types missing in this list (serverless rule types only)
@mikecote mikecote added Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) labels Apr 16, 2024
@elasticmachine
Copy link
Contributor

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

@mikecote mikecote moved this from Awaiting Triage to Todo in AppEx: ResponseOps - Execution & Connectors Apr 18, 2024
@mikecote mikecote added the response-ops-ec-backlog ResponseOps E&C backlog label Nov 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
blocked Feature:Alerting response-ops-ec-backlog ResponseOps E&C 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
2 participants
@mikecote @elasticmachine