check_haproxy.sh always reports CRITICAL
Bug #1949493 reported by
Stephan Pampel
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| charm-haproxy |
New
|
Undecided
|
Unassigned | ||
Bug Description
check_haproxy.sh always reports CRITICAL even if there are services available to forward requests to.
IMHO it would be better if the check was only CRITICAL if all services of a proxy are not reachable and WARNING if the proxy still has at least one working backend. That way we would only get a CRITICAL if there is a client/customer impact.
Related branches
lp://staging/~stephanpampel/charm-haproxy/charm-haproxy
- Stephan Pampel (community): Approve
- Junien Fridrick: Approve
- Canonical IS Reviewers: Pending requested
-
Diff: 167 lines (+82/-20)3 files modifiedconfig.yaml (+13/-6)
files/nrpe/check_haproxy.sh (+67/-13)
hooks/hooks.py (+2/-1)
| description: | updated |
To post a comment you must log in.
