-
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
Onboard Transaction Error Rate rule type with FAAD #179496
Onboard Transaction Error Rate rule type with FAAD #179496
Conversation
/ci |
/ci |
…n-error-rate-rule-to-faad
/ci |
Pinging @elastic/response-ops (Team:ResponseOps) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
verified locally, works as expected
Pinging @elastic/obs-ux-infra_services-team (Team:obs-ux-infra_services) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
…n-error-rate-rule-to-faad
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Verified creating a new rule in this branch and updating an existing rule with alerts from main
work as expected.
💚 Build Succeeded
Metrics [docs]
History
To update your PR or re-run it, just comment with: cc @doakalexi |
Towards: #169867
This PR onboards the Transaction Error Rate rule type with FAAD.
To verify
Example:
.internal.alerts-observability.apm.alerts-default-000001
Example:
Recover the alert by setting
threshold: 200
The alert should be recovered and the AAD in the above index should be updated
kibana.alert.status: recovered
.