thegreenrobot

custom_metrics:
    
    - name: sqlserver.buffer.page_lookups
      counter_name: Page lookups/sec

    - name: sqlserver.buffer.page_reads
      counter_name: Page reads/sec

    - name: sqlserver.workload.queued_requests
      counter_name: Queued Requests

thegreenrobot

Log Processing Rules

log_processing_rules:

Generic String: "sensitive-info"

  - type: exclude_at_match
    name: exclude_sensitive_info
    pattern: (?:sensitive\-info)

thegreenrobot

A SaltStack AWS Auto Scaling Solution

Overview

The AWS Auto Scaling Goup, configured with a customised Cloud-Init file, sends a notification to an SNS Topic, which in turn passes it onto an SQS queue that the Salt Master is subscribed to. A Reactor watches for the auto scaling events and pre-approves the new minion based on its Auto Scaling group name and instance ID.

Salt Master Configuration

thegreenrobot

## credit: http://fabian-affolter.ch/blog/the-lineinfile-module-of-ansible/
--- 
- hosts: alpine_install
  user: root
 
  tasks:
#  - name: create a complete empty file
#    command: /usr/bin/touch /test/test.conf
 
  - name: create a new file with lineinfile

thegreenrobot

Keybase proof

I hereby claim:

• I am thegreenrobot on github.
• I am thematthewgreen (https://keybase.io/thematthewgreen) on keybase.
• I have a public key ASA1Qep_BhqXMlX3Ck-TRmr_Nb44oOnjzqJREnr16A7UDQo

To claim this, I am signing this object:

thegreenrobot

#System Design Cheatsheet

Picking the right architecture = Picking the right battles + Managing trade-offs

##Basic Steps

1. Clarify and agree on the scope of the system

• User cases (description of sequences of events that, taken together, lead to a system doing something useful)
  • Who is going to use it?
  • How are they going to use it?

thegreenrobot

// Use Gists to store code you would like to remember later on
console.log(window); // log the "window" object to the console