Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Sign up for free
Menu
Search
Features
All features
Private URLs
Password Protection
Custom URLS
Scheduled publishing
Remove Branding
Restrict embedding
Deck Collections
Notes
Features
All features
Private URLs
Password Protection
Custom URLS
Scheduled publishing
Remove Branding
Restrict embedding
Deck Collections
Notes
Explore
Featured decks
Featured speakers
Programming
Technology
Storyboards
Explore
Featured decks
Featured speakers
Programming
Technology
Storyboards
Pricing
Search
Sign in
Sign up for free
The Importance of Observability for Kafka-based...
Search
Jorge Quilcate
September 10, 2018
Programming
2.3k
2
Share
Embed
Copy iframe code
Copy JS code
Copy link
Start on current slide
The Importance of Observability for Kafka-based applications with Zipkin
https://github.com/jeqo/talk-kafka-zipkin
Jorge Quilcate
September 10, 2018
More Decks by Jorge Quilcate
See All by Jorge Quilcate
Making sense of Event-Driven Systems
jeqo
0
230
Making sense of event-driven dataflows - Kafka Summit NYC 2019
jeqo
0
710
distributed tracing and observability for your integration platform - OUGN 2018
jeqo
0
140
Reactive Patterns and Distributed Systems - OUGN 2018
jeqo
0
160
Increasing Observability with Distributed Tracing
jeqo
0
330
Observando Sistemas Distribuidos - PeruJUG
jeqo
1
500
From Messaging to Logs with Apache Kafka - OUGN17
jeqo
0
490
Scale WebLogic, the Kubernetes way - OUGN17
jeqo
1
830
De Mensajería hacia Logs con Apache Kafka - PeruJUG
jeqo
1
450
Other Decks in Programming
See All in Programming
KiroのSpecで「五目並べ」を作ってみる
satoshi256kbyte
1
380
作れる、でも消せるか?──安全に「枯らして消す」機能削除術 / Drain, Then Delete
chobishiba
2
780
コードで差別化できない時代の ソフトウェアエンジニアリング / Software Engineering in an Era Where Code Doesn’t Differentiate
kishida
2
180
Herb in Rails 8.2: Your ERB views, now HTML-aware @ Rails World 2026, Austin, Texas
marcoroth
0
220
phperだってパンチカードでコーディングしたい
o0h
PRO
0
340
Rでドレミ/Do-Re-Mi_with_R
florets1
0
130
sbt 2.0: takeoff
eed3si9n
0
160
Herb in Rails 8.2: Your ERB views, now HTML-aware @ Kaigi on Rails 2026, Tokyo, Japan
marcoroth
2
270
3回つくってわかった、 定期実行ジョブ基盤の本質情報
takai
0
510
Augmenting AI with the Power of Jakarta EE
ivargrimstad
0
220
AIで開発が速くなった先で、開発チームは何を目指すか
shihochan
0
1.5k
なぜCTOを降りてFDEを選んだのか?〜なぜプロダクト企業がFDEで顧客の現場に踏み込むのか〜
gonta
1
220
Featured
See All Featured
Why Your Marketing Sucks and What You Can Do About It - Sophie Logan
marketingsoph
0
430
Have SEOs Ruined the Internet? - User Awareness of SEO in 2025
akashhashmi
0
520
Building a A Zero-Code AI SEO Workflow
portentint
PRO
0
780
Embracing the Ebb and Flow
colly
88
5.2k
Sharpening the Axe: The Primacy of Toolmaking
bcantrill
46
3k
Cheating the UX When There Is Nothing More to Optimize - PixelPioneers
stephaniewalter
287
14k
Lightning Talk: Beautiful Slides for Beginners
inesmontani
PRO
2
730
エンジニアに許された特別な時間の終わり
watany
109
250k
Prompt Engineering for Job Search
mfonobong
0
520
Refactoring Trust on Your Teams (GOTO; Chicago 2020)
rmw
35
3.8k
Product Roadmaps are Hard
iamctodd
55
13k
The Illustrated Children's Guide to Kubernetes
chrisshort
51
53k
Transcript
The Importance of Observability for Kafka-based applications with Zipkin
[email protected]
Jorge Quilcate-Otoya @jeqo89 github.com/jeqo github.com/sysco-middleware Middleware team at SYSCO AS
focused on Data-Integration and Distributed Tracing
SYSCO AS Middleware department: Integration and Data Engineering We are
hiring! Partners: github.com/sysco-middleware sysco.no/
Agenda Event-Driven Applications and Kafka Observability and Distributed Tracing Simulating
Observability tools
Apache Kafka “Apache Kafka® is a distributed Streaming platform.”
Event-Driven Applications and Kafka Amazonas river
Event-Driven Architectural Style https://docs.microsoft.com/en-us/azure/architecture/guide/architecture-styles/event-driven
Service Collaboration and Dataflow Svc Svc Svc Svc Orchestration Event
Bus Svc Svc Svc Svc Choreography
https://www.slideshare.net/ConfluentInc/etl-is-dead-long-live-streams Kafka Ecosystem
Observability and Distributed Tracing Titicaca Lake
What is Observability? “In control theory, observability is a measure
of how well internal states of a system can be inferred from knowledge of its external outputs.” - Wikipedia
Observability is for *Unknown Unknowns* https://twitter.com/mipsytipsy/status/963956028940234752
Observability methods
Observability methods
Span = execution of a task Trace = tree of
spans Context Propagation = pass trace context between distributed components (e.g. HTTP Headers, Kafka-record Headers) Distributed Tracing Concepts
Demo Lab 01: Hello world to Distributed Tracing • Tracing
concepts • Brave instrumentation https://github.com/jeqo/talk-kafka-zipkin#lab-1-hello-world-distributed-tracing
Adoption approaches Annotation-based - Part of your code - Instrument
libraries first - Add custom spans on-demand - Check benchmarks Black-box
How does it work? Svc 0 Svc 1 tracer tracer
Collector Tracing System Tracing DB
Zipkin Architecture
Demo Lab 02: Tracing Kafka-based applications • Kafka-clients and Kafka-streams
instrumentation • Kafka Interceptors for Kafka Connectors https://github.com/jeqo/talk-kafka-zipkin#lab-02-twitter-kafka-based-application
Adoption approaches Annotation-based - Part of your code - Instrument
libraries first - Add custom spans on-demand - Check benchmarks Black-box - Agent-based model - Framework/Protocol support - Machine impact - Promising approach: Service Mesh/Sidecar Proxy
Service Meshes and Zipkin
#QOTD https://twitter.com/rakyll/status/971231712049971200
Simulating Observability tools Lima - Chorrillos
➔ Model your architecture ➔ Simulate interaction ➔ Generate Traces
➔ Visualize your system’s traffic with Vizceral “SimianViz/ Spigo” - Simulation Protocol Interaction in GO github.com/adrianco/spigo
"Monitoring Microservices: A Challenge" - Adrian Cockcroft
Models from Traces, e.g. Vizceral https://www.youtube.com/watch?v=jWpI8qzqNHk
Demo Lab 03: Spigo and Vizceral • Spigo for Simulation
of Architecture behavior • Zipkin for Tracing and Vizceral for Traffic Monitoring https://github.com/jeqo/talk-kafka-zipkin#lab-3-spigo-simulation
Takeaways ➔ If are doing Distributed Systems — using Kafka
or not — consider Distributed Tracing. ➔ Instrument libraries first, not your code. ➔ Experiment by simulating your deployment. ➔ How many models can you build from tracing data?!
References Papers - Dapper: https://static.googleusercontent.com/media/research.google.com /en//pubs/archive/36356.pdf - Canopy: http://cs.brown.edu/~jcmace/papers/kaldor2017canopy.pdf -
Automating Failure Testing Research at Internet Scale: https://people.ucsc.edu/~palvaro/socc16.pdf Posts: - Logging v. Instrumentation https://peter.bourgon.org/blog/2016/02/07/logging-v-instrument ation.html - Monitoring and Observability https://medium.com/@copyconstruct/monitoring-and-observability -8417d1952e1c - Monitoring in the Time of Cloud Native https://medium.com/@copyconstruct/monitoring-in-the-time-of-cl oud-native-c87c7a5bfa3e Tools: - Zipkin: https://zipkin.io/ - Brave: https://github.com/openzipkin/brave - Kafka Interceptors: https://github.com/sysco-middleware/kafka-interceptors - Spigo: https://github.com/adrianco/spigo - Vizceral: https://github.com/Netflix/vizceral
Thanks! Q&A github.com/jeqo/talk-kafka-zipkin github.com/sysco-middleware Machu Picchu