Bug 1290646 - Allow trivial monitoring of kill switch
Summary: Allow trivial monitoring of kill switch
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Bugzilla
Classification: Community
Component: Internal Tools
Version: 4.4
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ---
Assignee: PnT DevOps Devs
QA Contact: tools-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-12-11 03:01 UTC by Will Thames
Modified: 2016-08-16 01:35 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-06 03:04:23 UTC
Embargoed:


Attachments (Terms of Use)

Description Will Thames 2015-12-11 03:01:44 UTC
Provide a mechanism to monitor whether the kill switch is enabled. 

This could be as simple as 

http://bugzilla.example.com/kill_switch_status

but as long as it's easy to determine the status, I'm not particularly concerned about the implementation details. 

I don't believe the state of the switch is particularly sensitive (even if the reason for the state might be) - so I would hope that the status would be available without logging in.

Comment 1 Jason McDonald 2015-12-11 03:13:10 UTC
(In reply to Will Thames from comment #0)
> I don't believe the state of the switch is particularly sensitive (even if
> the reason for the state might be) - so I would hope that the status would
> be available without logging in.

FWIW, I agree that the kill switch state is not secret.  In the original design, we only showed the state of the kill switch to users in the rule-engine group because they were the only users who could do something about it.  Unfortunately, we didn't consider the possibility of a monitoring system wanting to see the state.

Comment 2 Jeff Fearn 🐞 2016-06-16 02:11:56 UTC
I think this should be done as a DB query

"select count(*) > 0 from rh_rule_state where when_enabled IS NULL"

Comment 3 Jeff Fearn 🐞 2016-07-06 03:04:23 UTC
As I said in #2 this should be done by adding that sql to the monitoring system.


Note You need to log in before you can comment on or make changes to this bug.