Главная
Study mode:
on
1
Intro
2
Service ownership, defined
3
Obstacles to successful service ownership
4
Distributed tracing, defined
5
Relationships matter
6
Traces = raw material, not finished product
7
Centralized documentation
8
Why is documentation important?
9
Iterating toward ownership
10
More context -- mitigating facter
11
Dynamic alert delivery
12
Handling alerts
13
Improving postmortems
14
Postmortems are documentation
15
Why is improving oncall important?
16
Determining SLOS
17
Derive internal SLOs using tracing
18
Why are SLOs important?
19
3-piece puzzle review
20
Making changes
21
Ownership = Accountability + Agency
Description:
Explore a comprehensive conference talk on building distributed service ownership in software development teams. Learn strategies for transitioning from monolithic teams to distributed ownership models, including effective documentation practices, oncall responsibility distribution, and clear objective setting. Discover the balance between human-driven processes and automated telemetry-based systems. Understand the critical role of team agency in successful service ownership, and gain insights into implementing distributed tracing, centralized documentation, dynamic alert delivery, and SLO determination. Examine the importance of postmortems as documentation and the three-piece puzzle of ownership, accountability, and agency in creating scalable people systems for operating software at scale.

Building Service Ownership Using Documentation, Telemetry, and a Chance to Make Things Better

USENIX
Add to list