The document discusses observability in microservices and provides an overview of key concepts. It introduces One Concern, which monitors buildings and natural disasters, and describes the differences between monoliths and microservices. It then covers the three pillars of observability - monitoring, logging, and tracing - and provides examples of tools for each. The rest of the document focuses on Jaeger, describing its architecture, benefits, features, terminology, and includes a demo. It concludes by mentioning One Concern is hiring.
About me
● Workingas Software engineer and leading India office for One Concern
● Worked with Flipkart & Arvind group
● Apache committer for project Apache gossip
● Speaker at Meetups & Conferences
Coordinates:
Email: chandresh@oneconcern.com
Linkedin: https://www.linkedin.com/in/chandresh-pancholi-467a8015/
3.
About One Concern
Oneconcern is a multi-hazard platform which is on the mission of saving lives and
build resilience & livelihood everywhere.
Our platform provides unprecedented situational awareness and actionable insights
for decision-makers.
One Concern currently monitors 12,076,661 residential and 651,917 commercial
buildings. We monitor earthquakes for 36M people.
website: https://oneconcern.com
Jaeger features
● Usesconsistent upfront sampling with individual per service/endpoint
probabilities
● Multiple storage backends: Cassandra, Elasticsearch, memory.
● Adaptive sampling
● Post-collection data processing pipeline
● Libraries available in Java, GO, Node, Python, C++
16.
Terminology
● Span ⇒A span represents a logical unit of work in Jaeger that has an operation
name, the start time of the operation, and the duration. Spans may be nested
and ordered to model causal relationships.
● Trace ⇒ A trace is a data/execution path through the system, and can be
thought of as a directed acyclic graph of spans.