thresholds in check_graylog_health.py should be configurable
Bug #1809278 reported by
Gareth Woolridge
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Graylog Charm |
Fix Released
|
Medium
|
Unassigned |
Bug Description
The thresholds for the various components of check_graylog_
For the uncommitted_msgs for instance this is hard coded to 100 - which is rather low for a cluster with any load running within a contended cloud.
Ideally we should expose these values in juju config.
For instance in prod-comms-logging we've cowboyed to 1000 to stop the alert firing in "normal" operation.
Changed in graylog-charm: | |
status: | Incomplete → Opinion |
status: | Opinion → Won't Fix |
status: | Won't Fix → Triaged |
importance: | Undecided → Medium |
To post a comment you must log in.
There's the nagios_ uncommitted_ {warn|crit} knob in current charm versions, is there anything else that is missing?