Observability is the ability to measure a system’s current state based on the data it generates, recorded as logs, metrics, and traces. Logs, metrics, and traces are known as the “three pillars of observability.”
Logs: Logs record the details of an event.
Metrics: Metrics capture the numeric measurements used to quantify the performance and health of services.
Traces: Traces track how services connect from end to end in response to requests.
Implement observability using a combination of instrumentation methods, including open-source instrumentation tools, such as OpenTelemetry.
Observability: The ability of a system to provide deep insights into its internal state, often focusing on unknown issues.
Monitoring: Actively tracking predefined metrics and thresholds to ensure system health.
Telemetry: The process of collecting and transmitting data from remote (or) inaccessible sources.
Observability helps cross-functional teams understand and answer specific questions about what’s happening in highly distributed systems.
I have completed an Observability Series.
Day-1 Fundamentals of Observability ✅ Theory
Day-2 Metrics, Monitoring, and Prometheus | Basics of Prometheus ✅ Theory
Day-3 Prometheus Explanation ✅ Theory
Day-4 Custom Metrics ✅ Theory
Day-5 Logging with EFK Stack | Elastic Search, FluentBit and Kibana ✅ Theory
Day-6 Distributed Tracing ✅ Theory
Day-7 End-to-End Observability Project ✅ 🗞️ Theory ✍ Hands-On
Top comments (0)