Minimum Viable Ops

Building a new system involves a lot of infrastructure and monitoring decisions: where to host, how to deploy, and how to monitor your new application. There's a strong tendency to "do it right" from the get go. But trying to build the ultimate platform will slow down your progress in those crucial first days.

In this talk, we will discuss how to best approach all these decisions. We will explain the various layers of infrastructure you need to successfully run a system in production. These layers include logging, deployments, and monitoring. For each layer, we will discuss options for satifying the needs of those layers, and how those choices will change as your business grows. In the end, I hope to have given you a plan for how to build the first version of your operations platform and some ideas for how that platform will grow and change as your service grows and changes.

This talk was given at the AWS Popup Loft in San Francisco. Unfortunately, the talk was not recorded.

Transcript

1. 2/22/15 Minimum Viable Ops AWS LOFT FEBRUARY 2105
2. 2/22/15 POLICY AS CODE How is babby PagerDuty formed?
3. 2/22/15 POLICY AS CODE
4. 2/22/15 MINIMUM VIABLE OPS @dougbarth
5. 2/22/15 MINIMUM VIABLE OPS
6. 2/22/15 POLICY AS CODE Dev Ops
7. 2/22/15 MINIMUM VIABLE OPS Minimum Viable Ops
8. 2/22/15 MINIMUM VIABLE OPS
9. 2/22/15 MINIMUM VIABLE OPS
10. 2/22/15 MINIMUM VIABLE OPS Logging Metrics/Monitoring Incident Mangement Provisioning Deployments Testing Production
11. 2/22/15 MINIMUM VIABLE OPS Perfect is a myth
12. 2/22/15 MINIMUM VIABLE OPS Start simple
13. 2/22/15 MINIMUM VIABLE OPS Have a goal
14. 2/22/15 MINIMUM VIABLE OPS Iterate
15. 2/22/15 MINIMUM VIABLE OPS Logging Metrics/Monitoring Incident Mangement Provisioning Deployments Testing Production
16. 2/22/15 MINIMUM VIABLE OPS Provisioning
17. 2/22/15 MINIMUM VIABLE OPS PaaS? VMs? Physical?
18. 2/22/15 MINIMUM VIABLE OPS Configuration Management
19. 2/22/15 MINIMUM VIABLE OPS
20. 2/22/15 MINIMUM VIABLE OPS Baking AMIs?
21. 2/22/15 MINIMUM VIABLE OPS Logging
22. 2/22/15 MINIMUM VIABLE OPS Get them off ASAP
23. 2/22/15 MINIMUM VIABLE OPS
24. 2/22/15 MINIMUM VIABLE OPS ELK Graylog
25. 2/22/15 MINIMUM VIABLE OPS Metrics/ Monitoring
26. 2/22/15 MINIMUM VIABLE OPS Collect from logs?
27. 2/22/15 MINIMUM VIABLE OPS
28. 2/22/15 MINIMUM VIABLE OPS statsd graphite
29. 2/22/15 MINIMUM VIABLE OPS Timeseries
30. 2/22/15 MINIMUM VIABLE OPS Transactional traces
31. 2/22/15 MINIMUM VIABLE OPS What to monitor?
32. 2/22/15 MINIMUM VIABLE OPS In & Out
33. 2/22/15 MINIMUM VIABLE OPS Everything else
34. 2/22/15 MINIMUM VIABLE OPS Incident Management
35. 2/22/15 MINIMUM VIABLE OPS Detecting
36. 2/22/15 MINIMUM VIABLE OPS Disk free Insane Load Low memory
37. 2/22/15 MINIMUM VIABLE OPS Customer impact
38. 2/22/15 MINIMUM VIABLE OPS What if you’re sleeping?
39. 2/22/15 MINIMUM VIABLE OPS Who is responsible?
40. 2/22/15 MINIMUM VIABLE OPS Give important customers a way to page you
41. 2/22/15 MINIMUM VIABLE OPS Deployments
42. 2/22/15 MINIMUM VIABLE OPS Script from the start
43. 2/22/15 MINIMUM VIABLE OPS Fabric
44. 2/22/15 MINIMUM VIABLE OPS Integrate with CM?
45. 2/22/15 MINIMUM VIABLE OPS Testing
46. 2/22/15 MINIMUM VIABLE OPS Continuous Integration
47. 2/22/15 MINIMUM VIABLE OPS
48. 2/22/15 MINIMUM VIABLE OPS Staging
49. 2/22/15 MINIMUM VIABLE OPS Canary deploys
50. 2/22/15 MINIMUM VIABLE OPS Failure Friday HTTPS://WWW.PAGERDUTY.COM/BLOG/FAILURE-FRIDAY-AT-PAGERDUTY/
51. 2/22/15 POLICY AS CODE pagerduty.com/jobs DOUG@PAGERDUTY.COM
52. 2/22/15 pagerduty.com/jobs Questions?