Richard Murillo rjmurillo

Monitoring

base rate fallacy: given 1% false positive, 1% false negative, and 99.9% uptime: 9.1% chance positive predictive value (true positive)
sensitivity (% true positives) vs specificity (% not false positive)
‘Alert liberally; page judiciously. Page on symptoms, rather than causes.’
‘An alert should communicate something specific about your systems in plain language: “Two Cassandra nodes are down” or “90% of all web requests are taking more than 0.5s to process and respond.”’
‘Not all alerts carry the same degree of urgency.’
‘Many alerts will not be associated with a service problem, so a human may never even need to be aware of them. […] should generate a low-urgency alert that is recorded in your monitoring system for future reference or investigation but does not interrupt anyone’s work.’

These are the Kickstarter Engineering and Data role definitions for both teams.

	// ghprb 1.29.2
	import java.lang.reflect.Field
	import jenkins.model.*
	import org.jenkinsci.plugins.ghprb.*

	def descriptor = Jenkins.instance.getDescriptorByType(org.jenkinsci.plugins.ghprb.GhprbTrigger.DescriptorImpl.class)

	Field auth = descriptor.class.getDeclaredField("githubAuth")

	auth.setAccessible(true)