The default operator for AlarmGnocchiThresholdRule is `eq`.
Bug #1707793 reported by
Martin Lopes
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Aodh |
Confirmed
|
Wishlist
|
Unassigned | ||
Bug Description
It might make sense to change the default operator in AlarmGnocchiThr
When creating a threshold alarm, I think the expectation is that it will raise events for any state that meets or exceeds the threshold. In my testing, using `eq` will only raise events if the CPU usage is exactly equal to the defined threshold.
As a workaround, the user can specify a custom operator when creating the alarm: "--comparison-
| Changed in aodh: | |
| assignee: | nobody → Martin Lopes (martinlopes) |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to aodh (master) | #1 |
| Changed in aodh: | |
| status: | New → In Progress |
| Changed in aodh: | |
| status: | In Progress → Won't Fix |
| status: | Won't Fix → Confirmed |
| importance: | Undecided → Wishlist |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Change abandoned on aodh (master) | #2 |
| Changed in aodh: | |
| assignee: | Martin Lopes (martinlopes) → nobody |
To post a comment you must log in.
Fix proposed to branch: master
Review: https:/