Observability / Monitoring

Notes

• Monitoring is the verb. You monitor your application

  • Observability is the property of the system; the ability to be observed

• No matter how great our monitoring smarts, they’ll count for little if folks don’t use them when designing, developing or testing their applications. Moreover, if a system can’t be applied in context of work being performed, it’ll just end up on the “too hard to use” shelf. (source)

• Observability is a measure of how well internal states of a system can be inferred from knowledge of its external outputs (source)

• Monitoring gives software teams instrumentation, which collects data about their systems and allows them to quickly respond when errors and issues occur. Observability, on the other hand, is the practice of instrumenting those systems with tools to gather actionable data that provides not only the when of an error or issue, but, more important, the why. (source)

• Telemetry in software refers to the ethical and transparent collection of user and usage data from software usually over the internet while adhering to stringent security and privacy standards throughout the process. (source)

Links

• Monitoring and Observability — What’s the Difference and Why Does It Matter? – The New Stack

• Telemetry in Software. There’s no getting away from telemetry… | by Vardhan Dugar | justDevTalk | Medium

• Profile a React App for Performance

• (MELT)

• OpenTelemetry