You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem?
When creating an alerting monitor on top of an anomaly detector, the alerting dashboard only provides an easy UI to add trigger conditions for anomaly grade and confidence. However there can be a lot of other aspects we might want to configure our alerts based on.
For example we can configure to trigger an alert based on the feature attribution of the anomaly or the gap between actual and expected value.
What solution would you like?
Adding improved UI on the trigger creation in alerting-dashboards with things like:
Checkbox to enable feature filtering
Enable filtering anomalies based on feature attribution.
drop down for feature selection
Select feature to filter by
Options:
memory_usage_percentage
cpu_usage_percentage
Slider input for attribution threshold:
0.0 to 1.0 (for example: Exclude anomalies with an attribution for cpu_usage_percentage greater than 0.75).
Number input for percentage difference :
between actual and expected, place 30% difference between actual and expected. for example as a must as part of the trigger
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem?
When creating an alerting monitor on top of an anomaly detector, the alerting dashboard only provides an easy UI to add trigger conditions for anomaly grade and confidence. However there can be a lot of other aspects we might want to configure our alerts based on.
For example we can configure to trigger an alert based on the feature attribution of the anomaly or the gap between actual and expected value.
What solution would you like?
Adding improved UI on the trigger creation in alerting-dashboards with things like:
The text was updated successfully, but these errors were encountered: