Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
Map & Territory: A story of visibility
Search
Pierre-Yves Ritschard
April 19, 2013
Technology
1
1.3k
Map & Territory: A story of visibility
Pierre-Yves Ritschard
April 19, 2013
Tweet
Share
More Decks by Pierre-Yves Ritschard
See All by Pierre-Yves Ritschard
Meetup Camptocamp: Exoscale SKS
pyr
0
430
The (long) road to Kubernetes
pyr
0
310
From vertical to horizontal: The challenges of scalability in the cloud
pyr
0
65
Change Management at Scale
pyr
0
110
5 years of Clojure
pyr
2
1k
Taming Jenkins
pyr
0
48
Init: then and now
pyr
1
200
Billing the Cloud
pyr
0
300
From Vertical to Horizontal
pyr
2
140
Other Decks in Technology
See All in Technology
オーティファイ会社紹介資料 / Autify Company Deck
autifyhq
10
130k
Contributing to Rails? Start with the Gems You Already Use
yahonda
2
120
TLSから見るSREの未来
atpons
2
240
ClaudeCodeにキレない技術
gtnao
0
560
スタックチャン家庭用アシスタントへの道
kanekoh
0
110
Operating Operator
shhnjk
1
650
Delegating the chores of authenticating users to Keycloak
ahus1
0
180
AWS CDK 入門ガイド これだけは知っておきたいヒント集
anank
5
600
セキュアな社内Dify運用と外部連携の両立 ~AIによるAPIリスク評価~
zozotech
PRO
0
100
60以上のプロダクトを持つ組織における開発者体験向上への取り組み - チームAPIとBackstageで構築する組織の可視化基盤 - / sre next 2025 Efforts to Improve Developer Experience in an Organization with Over 60 Products
vtryo
3
980
対話型音声AIアプリケーションの信頼性向上の取り組み
ivry_presentationmaterials
2
690
SREの次のキャリアの道しるべ 〜SREがマネジメントレイヤーに挑戦して、 気づいたこととTips〜
coconala_engineer
1
1k
Featured
See All Featured
The Power of CSS Pseudo Elements
geoffreycrofte
77
5.9k
Build The Right Thing And Hit Your Dates
maggiecrowley
37
2.8k
Why You Should Never Use an ORM
jnunemaker
PRO
58
9.4k
Six Lessons from altMBA
skipperchong
28
3.9k
ピンチをチャンスに:未来をつくるプロダクトロードマップ #pmconf2020
aki_iinuma
126
53k
The Web Performance Landscape in 2024 [PerfNow 2024]
tammyeverts
8
700
RailsConf & Balkan Ruby 2019: The Past, Present, and Future of Rails at GitHub
eileencodes
138
34k
What’s in a name? Adding method to the madness
productmarketing
PRO
23
3.5k
Visualizing Your Data: Incorporating Mongo into Loggly Infrastructure
mongodb
47
9.6k
Mobile First: as difficult as doing things right
swwweet
223
9.7k
Become a Pro
speakerdeck
PRO
29
5.4k
Site-Speed That Sticks
csswizardry
10
700
Transcript
Map & Territory a story of visibility
Pierre-Yves @pyr https://github.com/pyr
https://exoscale.ch
Visibility
How do we work ?
None
How do we improve?
Avoid Shortcuts!
None
We want lower defect rates
We want to make informed decisions
Design Build Live
Visibility
Extracting meaningful state data from heterogeneous event sources, over time
Meaningful (relates to business value)
State Data (structured payload)
Heterogeneous (everyone is involved)
Over time (tracking)
How does it help my system's lifecycle ?
Map =/= Territory
Break out of our mental model
"I'll push this minor change, it cannot do any harm"
None
"I'll just add this static route"
None
Better lifecycle Informed decisions Better maps
Systems are (increasingly) complex
Web Infrastructure circa 00 (2 servers)
Visibility Circa '00
Web Infrastructure circa '12 (27 nodes)
None
Visibility Circa '12
Q: how is business doing today ? A:
Q: how is business doing today ? A: based on
these key metrics we're looking good
Figure out those key metrics
We need appropriate tooling
events across: system, components, software
The event stream approach
Plenty of small producers Few big consumers
Production: Anything that happens or moves (logs too!): Normalize &
Stream
Consumption: Aggregate Correlate Decide
Aggregation compute compound metrics (ratios, sums)
Correlation
Decision track, alert, ignore, scale
Implementing on premise, saas or in between ?
SaaS loggly, papertrail, librato, datadog, ...
On Premise collectd, logstash, graphite, statsd, riemann
The path to visibility: Find key metrics Find the right
tools Rely on an event stream Involve everyone Challenge your mental model Hopefully, improve quality and lower defect rates in the process!
Questions ?