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
2
44k
低レイヤソフトウェア技術者が YouTuberとして食っていこうとした話
sat
PRO
3
3k
クラウド開発の舞台裏とSRE文化の醸成 / SRE NEXT 2025 Lunch Session
kazeburo
1
610
対話型音声AIアプリケーションの信頼性向上の取り組み
ivry_presentationmaterials
3
1.1k
SREのためのeBPF活用ステップアップガイド
egmc
2
1.3k
CDK Vibe Coding Fes
tomoki10
1
640
AIコードアシスタントとiOS開発
jollyjoester
0
120
LLM拡張解体新書/llm-extension-deep-dive
oracle4engineer
PRO
24
6.5k
AI エージェントと考え直すデータ基盤
na0
20
8k
全部AI、全員Cursor、ドキュメント駆動開発 〜DevinやGeminiも添えて〜
rinchsan
10
5.2k
衛星運用をソフトウェアエンジニアに依頼したときにできあがるもの
sankichi92
1
1.1k
Frontier Airlines Customer®️ USA Contact Numbers: Complete 2025 Support Guide
frontierairlineswithflyagent
0
100
Featured
See All Featured
Git: the NoSQL Database
bkeepers
PRO
430
65k
Why You Should Never Use an ORM
jnunemaker
PRO
58
9.5k
How To Stay Up To Date on Web Technology
chriscoyier
790
250k
Typedesign – Prime Four
hannesfritz
42
2.7k
Testing 201, or: Great Expectations
jmmastey
43
7.6k
Optimizing for Happiness
mojombo
379
70k
Thoughts on Productivity
jonyablonski
69
4.7k
Adopting Sorbet at Scale
ufuk
77
9.5k
The Pragmatic Product Professional
lauravandoore
35
6.7k
Building an army of robots
kneath
306
45k
Bootstrapping a Software Product
garrettdimon
PRO
307
110k
Visualization
eitanlees
146
16k
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 ?