thresholds in check_graylog_health.py should be configurable

Bug #1809278 reported by Gareth Woolridge
12
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_health.py are hard coded for what is WARBN vs CRITICAL.

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.

Revision history for this message
Peter Sabaini (peter-sabaini) wrote :

There's the nagios_uncommitted_{warn|crit} knob in current charm versions, is there anything else that is missing?

Changed in graylog-charm:
status: New → Incomplete
Paul Goins (vultaire)
Changed in graylog-charm:
status: Incomplete → Opinion
status: Opinion → Won't Fix
status: Won't Fix → Triaged
importance: Undecided → Medium
Revision history for this message
Xav Paice (xavpaice) wrote :

nagios_uncommitted_warn and nagios_uncommitted_crit covers the request in this bug.

Changed in charm-graylog:
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.