With emergence of DevOps approach to application development, deployment and management developers get more and more involved in day-to-day system operations. Lately, there has been a popular point of view that developers should be included in oncall rotation on equal grounds with sys admins. While I don't fully subscribe to that mentality, there are certain processes that must be implemented by every organization to get developers involved in production operation of the software they built. In this talk I'll walk through different aspects of operational oncall responsibilities and discuss ways in which developers should (and should not) be involved in operation of production systems.

1. N CALL
FOR
DEVELOPERS
@papa_fire

2. MY NAME IS LEON
HELLO
and I am a developer

3. user:/$~ sudo -s
bash: Permission denied
user is not in the sudoers file.
This incident will be reported.

4. user:/$~ sudo -s
root:/#~
F&*# YEAH!

5. WITH GREATPOWER
COMES GREATRESPONSIBILITY
(and more work)

6. This Is Where
Your Awesome
TITLE GOES
Should
Developers
Be
On Call?

7. hardware
network
application
performance
process
Things
that can
go wrong
security

8. alert escalation resolution
ONLY ONE HAS TO SUFFER

9. 1
2
3
can I fix it?
can I fix it tomorrow?
do I care?
ACTIONABLE ALERTS

10. ACTIONABLE ALERTS
1
2
3
can I fix it?
can I fix it tomorrow?
do I care?
4 can someone else fix it?

11. …AND?

12. Create An
Epic Slideshare
With This
TEMPLATE
documentation
documentation
documentation

13. SAY NOTO
UNDOCUMENTED
ALERTS

14. DEEP INSTRUMENTATION
top-down approach
understand business1
2
3
monitor business
correlate data

15. network latency
conversions
database load
revenue
email bounce rate
performance
MONITOR EVERYTHING - ALERT ON WHAT’S IMPORTANT
CPU load
cache hit ratio
API responsiveness

16. CONSTANT INSTRUMENTATION
monitoring
is NOT
a feature

17. CONTINUOUS
IMPROVEMENT

18. availability
(determine the need)
(deploys, special events)
which one?
AVAILABILITY

19. BEA
GOODCITIZEN

20. @papa_fire