Need of Instrumentation 🤔

• How do you know your application is running fine?
• SLAs
• Customer satisfaction
• Good night’s sleep without worrying all the time 😴
• Hope is not a strategy

<aside> 💡 The Reliability mandate starts with Instrumentation - You can only improve what you measure.

</aside>

Landscape of Instrumentation 🌈

• Your application is not alone.
• Its actually a 🍔 Burger which has
  • The Bun(Cloud/VM)
  • Patty(application)
  • Along with Mayo sauce(RDS/DB)
  • And Ketchup(Third party services)
• Throw in some more 🍔 burgers that you eat run together and you go into the rabbit hole of “Full stack observability”!

<aside> 💡 Modern applications are like living organisms that grow and shrink in all possible directions and also communicate with their friends and relatives.

</aside>

Bow in the Temple of Observability 🙇🏻

Adoption order is not the same as below.

• Traces
  • Adoption is difficult
• Events
  • Critical for co-relation.
  • Need precision storage, can’t loose them.
• Metrics
  • Adoption is easy with consistency
  • No root cause analysis
• Profiling
  • Special case
  • On Demand
• Logs
  • Adoption is easy but no consistency
  • Need to be a domain expert
• Exceptions
  • Kind of like structured logging.
  • Depends a lot on tooling on the consumption side.