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

Create guidelines for connector type owners to know how and when to flag user type errors #180957

Open
5 tasks
mikecote opened this issue Apr 16, 2024 · 1 comment
Open
5 tasks
Labels
Feature:Actions Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)

Comments

@mikecote
Copy link
Contributor

mikecote commented Apr 16, 2024

Now that our metrics can distinguish between systematic errors and user errors, we should create guidelines for connector type owners to go through and flag user errors accordingly. Having guidelines will allow for consistent flagging across connector types and explain the importance of them.

Depends on: #180419

Definition of Done:

  • Guidelines contains a breakdown of HTTP status codes that should be flagged as user errors
  • Guidelines contains the definition of a user error and the level of accuracy required before defining errors as user errors
  • Guidelines contains the context and importance of properly flagging user errors
  • Guidelines contains code examples to flag and test the user errors
  • Connector best practices updated with our guidelines and how-to for flagging user errors (https://docs.elastic.dev/reops/developer-guide/best-practices-connectors)

cc @kobelb @heespi

@mikecote mikecote added Feature:Actions 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)

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

No branches or pull requests

2 participants