Raise your hand if you enjoy being buried in alerts or woken up at 2 a.m. — yeah … thought so. Ever-rising customer expectations around high availability and performance put massive pressure on the teams who develop and support SaaS products. And teams are literally losing sleep over it. Until outages and other incidents are a thing of the past, organizations need to invest in a way of dealing with them that won’t lead to burn-out. In this session, you’ll learn how to combine the latest tooling with DevOps practices in the pursuit of a sustainable incident response workflow. It’s all about transparency, actionable alerts, resilience and learning from each incident.

1. How to build a healthy
on-call culture
SERHAT CAN | TECHNICAL EVANGELIST | ATLASSIAN | @SRHTCN

2. https://unsplash.com/photos/yO3whNbzxsc
2014 failure: https://www.theverge.com/2014/10/3/6414949/911-call-failures-fcc
2018 failure: https://edition.cnn.com/2018/12/28/us/centurylink-outage-911-calls/index.html

3. ON-CALL CAN BE A SOURCE OF
STRESS AND BURNOUT.
https://unsplash.com/photos/Of8C-QHqagM

4. The analysis revealed significant effects
of extended work availability on the daily
start-of-day mood and cortisol awakening
response.
EXTENDED WORK AVAILABILITY AND ITS RELATION WITH START-OF-DAY MOOD AND CORTISOL.
J OCCUP HEALTH PSYCHOL.
2016 JAN;21(1):105-18. DOI: 10.1037/A0039602. EPUB 2015 AUG 3.

5. https://www.atlassian.com/blog/software-teams/modern-software-development-trends

6. https://en.dopl3r.com/memes/hot-topics/microservices/247404

7. You build it, you run it.
DR. WERNER VOGELS, CTO AMAZON

8. Dev - Ops