Observability
Explore how to implement observability in microservices by understanding metrics, logs, and traces. Learn to monitor service health, diagnose issues, and handle challenges unique to event-driven architectures.
It’s prudent to start with a clear definition of observability. It means to be able to notice or discern something. Applied to our focus on software applications, we can be more specific about what we discern and how we do so: to be able to measure the internal state of a system by its outputs.
In software systems, this is achieved through the enablement of what is commonly referred to as the three pillars of observability:
Metrics: A series of measurements over time
Logs: A record of messages describing noticeable events within a system
Traces: A set of indicators throughout logs that connect a series of related events
At this point, it’s worth addressing the critical commentary ...