Bug 1290646

Summary:	Allow trivial monitoring of kill switch
Product:	[Community] Bugzilla	Reporter:	Will Thames <wthames>
Component:	Internal Tools	Assignee:	PnT DevOps Devs <hss-ied-bugs>
Internal Tools sub component:	Rules Engine	QA Contact:	tools-bugs <tools-bugs>
Status:	CLOSED WONTFIX	Docs Contact:
Severity:	medium
Priority:	high	CC:	mtahir, wthames
Version:	4.4
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-07-06 03:04:23 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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.