Upgrade to Pro — share decks privately, control downloads, hide ads and more …

A Whirlwind Tour of Etsy's Monitoring Stack

A Whirlwind Tour of Etsy's Monitoring Stack

It's no secret that at Etsy we are big fans of small, incremental and frequent changes and tight feedback loops. This is how we make it possible to deploy changes to our main codebase more than 50 times a day and also safely apply changes to our infrastructure in a continuous fashion. It enables us to rapidly fix bugs and roll out features in our application stack and infrastructure. This however would not be possible without a tight feedback loop and a myriad of monitoring tools that keep us informed about changes and
possible problems in every nook and cranny of the Etsy stack, no matter if it's a network change event, systems or application level performance or how bad the last week of on-call rotation was.

Daniel Schauenberg

May 06, 2014

More Decks by Daniel Schauenberg

Other Decks in Technology


  1. @mrtazz Ganglia • System level metrics • Instance per DC/environment

    • > 220k RRD files • Fully configured through Chef role attributes
  2. @mrtazz StatsD • Single instance on one server • Traffic

    mostly from 70 Web & 24 API servers • Node.js • Heavy Sampling • Graphite as backend
  3. @mrtazz Graphite • Application level metrics • 96G RAM, 20

    Cores, 7.3T SSD RAID 10 • 525k metrics/minute • Mirrored Master/Master Setup • Functionally sharded relays
  4. @mrtazz Syslog-Ng • Web, Search, Gearman, Photos, Nagios, Network, VPN

    • 1.2GB written/minute • Chef role attribute based config • Rule ordering!
  5. @mrtazz Splunk • Indexes all of our log files •

    Easy search for patterns • Saved searches for interesting ones • Basically using it as a glorified grep
  6. @mrtazz Logstash • Experiment status • Makes it easier integrate

    different sources • Easy to set up in dev environment • Trying to figure out where/how it fits into our infrastructure
  7. @mrtazz Eventinator • Tracks all events in our infrastructure •

    Chef runs and changes • DNS changes • Network • Deploys • Server provisioning and decommissioning • ~ 12 million events in the last 2 years
  8. @mrtazz Chef • rules everything around me • Same cookbooks

    on prod and dev • every node runs Chef every 10 minutes • ton of knife plugins and handlers
  9. @mrtazz Nagios • 2 instances in each DC/environment • Fully

    Chef generated configuration • Service checks and contacts in git • Notifications via email->SMS gateway • ~75% ops on-call
  10. @mrtazz Nagios Herald • Add context to nagios alerts •

    What are the first 5 things you do when you get paged? • You already have the phone in your hand • nagios notification handler
  11. @mrtazz Summary • Set of trusted tools • Enhance where

    they come short • Try out new things • Write tools where applicable • Continuous monitoring and adaptation