-
Notifications
You must be signed in to change notification settings - Fork 8.1k
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
[Alerting] Add outside range ("is not between") comparator to UI #64220
Labels
enhancement
New value added to drive a business result
Feature:Alerting
Team:ResponseOps
Label for the ResponseOps team (formerly the Cases and Alerting teams)
Comments
Zacqary
added
enhancement
New value added to drive a business result
Feature:Alerting
Team:ResponseOps
Label for the ResponseOps team (formerly the Cases and Alerting teams)
labels
Apr 22, 2020
Pinging @elastic/kibana-alerting-services (Team:Alerting Services) |
3 tasks
We already have this in the API - it seemed like it was missing when I added the index threshold comparators, but we didn't end up adding it to the UI: kibana/x-pack/plugins/alerting_builtins/server/alert_types/index_threshold/alert_type.ts Lines 157 to 166 in c0c3e76
|
Zacqary
changed the title
[Alerting] Add outside range ("is not between") comparator
[Alerting] Add outside range ("is not between") comparator to UI
Apr 22, 2020
@pmuellr Updated issue to reflect that this needs to be added to the UI |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
enhancement
New value added to drive a business result
Feature:Alerting
Team:ResponseOps
Label for the ResponseOps team (formerly the Cases and Alerting teams)
In #63993 Metrics added a custom comparator called
OUTSIDE_RANGE
, which basically acts as the opposite ofBETWEEN
. Instead of alerting when a value is>= x && <= y
, it alerts when a value is< x || > y
.This can be added to
builtInComparators
and removed from Metrics'customComparators
so that all alert types can make use of it.The text was updated successfully, but these errors were encountered: