check_haproxy_queue_depth.sh maximum queue is alerting until haproxy is reloaded
Bug #1870312 reported by
Benjamin Allot
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
charm-haproxy |
Fix Released
|
Wishlist
|
Benjamin Allot |
Bug Description
When the maximum queue of a backend goes above 100, it needs "haproxy reload" to reset the max and clear the alert.
If the idea behind the check is to alert someone when an unusual amount of queue threshold has been reached, maybe we could add an informative message in the alert.
I proposed this MP as a solution: https:/
Regards,
Related branches
lp:~ballot/charm-haproxy/max_queue
- Tom Haddon: Approve
- Junien F: Approve
-
Diff: 18 lines (+6/-2)1 file modifiedfiles/nrpe/check_haproxy_queue_depth.sh (+6/-2)
Changed in charm-haproxy: | |
assignee: | nobody → Benjamin Allot (ballot) |
importance: | Undecided → Wishlist |
status: | New → In Progress |
Changed in charm-haproxy: | |
status: | In Progress → Fix Committed |
Changed in charm-haproxy: | |
status: | Fix Committed → Confirmed |
status: | Confirmed → Fix Released |
To post a comment you must log in.