jssjr

TOP COMMENTERS (github)
--------------------------------------------------------------------------------
sytse               70 of 16773 (  0%)  ######################################################################
homakov             61 of 16773 (  0%)  #############################################################
DanBC               50 of 16773 (  0%)  ##################################################
facepalm            46 of 16773 (  0%)  ##############################################
malandrew           46 of 16773 (  0%)  ##############################################
nailer              42 of 16773 (  0%)  ##########################################
masklinn            39 of 16773 (  0%)  #######################################
rmc                 38 of 16773 (  0%)  ######################################

jssjr

case "$(sw_vers -productVersion)" in
10.5.*|10.6.*)
  alias flush_dns="sudo dscacheutil -flushcache"
  ;;
10.8.*|10.7.*)
  alias flush_dns="sudo killall -HUP mDNSResponder"
  ;;
10.9.*)
  alias flush_dns="sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder"
  ;;

jssjr

• The Open Organization
• Art of Scalability
• Scalable Internet Architectures
• Web Operations
• The Goal
• Operations Management
• Leading Snowflakes

jssjr

jssjr

26798 1035 (sshd) access /proc/self/oom_score_adj read: 0 write: 2
26802 1035 (sshd) iotime /proc/self/oom_score_adj time: 3
27062 1035 (sshd) access /etc/ld.so.cache read: 0 write: 0
27099 1035 (sshd) access /lib/x86_64-linux-gnu/libwrap.so.0 read: 832 write: 0
27101 1035 (sshd) iotime /lib/x86_64-linux-gnu/libwrap.so.0 time: 2
27127 1035 (sshd) access /lib/x86_64-linux-gnu/libpam.so.0 read: 832 write: 0
27128 1035 (sshd) iotime /lib/x86_64-linux-gnu/libpam.so.0 time: 1
27155 1035 (sshd) access /lib/x86_64-linux-gnu/libselinux.so.1 read: 832 write: 0
27156 1035 (sshd) iotime /lib/x86_64-linux-gnu/libselinux.so.1 time: 1

jssjr

The Lifecycle of an Outage

Scott Sanders -- jssjr@github.com

---

So we're all here at Monitorama, and it's awesome to see so many incredible people in one place focusing on such an important topic. I'd like to talk a bit about outage lifecycles and how the monitoring and alerting tools we're familiar with can be woven into processes that enable confidence.

When an incident occurs, we typically have an increased risk of an outage. How we structure our initial response, our decision making process, and our communication directly affects the impact that this incident will have. We need to think critically about our ability to quickly resolve any problems and reduce the risk of future incidents.

jssjr

Keybase proof

I hereby claim:

• I am jssjr on github.
• I am jssjr (https://keybase.io/jssjr) on keybase.
• I have a public key whose fingerprint is 2081 E230 3001 6508 8847 1BBF A0A8 DB0F D1EA B94D

To claim this, I am signing this object:

jssjr

search(:node).map { |n| {fqdn: n['fqdn'], ip: n['ipaddress']} }.each do |i|

  Chef::Log.info "Creating: host #{i[:fqdn]}"

  djbdns_rr "host #{i[:fqdn]}" do
    fqdn i[:fqdn]
    cwd "#{node[:djbdns][:tinydns_dir]}/root"
    ip i[:ip]
    type "host"
    action :add

jssjr

jssjr

#autoload

vsnap() {
  trap "exit 1" INT
  if [[ $#@ -ne 2 ]] ; then
    echo 'usage: vsnap VM_NAME SNAPSHOT_DIR'
    return 1
  fi
  lastsnap="0"