boston devops meetup june 22nd

Confidential and Proprietary

Metrics, creating great outcomes since 2009

Mohit Dilawari

...through post mortems and school of hard knocks

Lessons Learned...

3

Define Metrics Upfront

● Typically think about throughput, Latency, SLA?

● What behavior are you changing?

● What is your measure of success?

4

Mining for metrics at Post-Mortems

5

Mining for metrics at Post-Mortems

MTTR > MTBF

6

Early Days

We had a few engineers and everyone knew our entire system

7

HQ

● Every service has one main dashboard

● Merge together system and business metrics

● Again, helps MTTR!!!

8

Percentiles

Guess what happened?

10

Raining Metrics

11

Drowning in Metrics

12

Metrics slimfast

13

Focus on symptoms

https://docs.google.com/document/d/199PqyG3UsyXlwieHaqbGiWVa8eMWi8zzAn0YfcApr8Q/edit

14

1 or 2 Key Metrics

15

Key Metric: Easy to understand

16

Make it visible

Outcomes

18

Metrics enable good culture

19

Connect engineers to business outcomes

20

Impacting Roadmap

21

Impacting Roadmap

22

Impact Roadmap

23

Better Code Coverage

https://github.com/yasyf/shamer

24

Justice Beaver

25

Driving Good Behavior

● In VPC?● Latest Java version● Readme● Linter configured● Average build times● Old PRs● Dead Branches● etc...

Wrap it up, dude!

27

Really?? An inspirational quote?

28

What did you say again?

● Think about metrics from start

● Mine for metrics

● Organize and be thoughtful about your key metrics

● Use metrics for internal systems

29

Questions?

Thanks!

Mohit Dilawari@mdilawari