Live webinarObservabilityProduction EngineeringLogging

Observability for your first production service

Your first service will break. Observability decides whether you know why.

Param Harrison

Param Harrison

Cofounder, AEOsome.com · Chief Mentor, learnwithparam.com

60 minutes · beginner
Add to calendarGoogleApple / iCal

Why this one matters

The difference between "something is broken" and "here is exactly what is broken" is observability. This session walks the three pillars: logs that tell a story, metrics that answer real questions, traces that show where time went. Aimed at the engineer shipping their first production service and wanting to sleep through the first on-call rotation.

Who should watch

  • Engineers shipping their first production service
  • Juniors going on-call without an observability stack
  • Teams moving from print-debugging to real production signals

What's on the menu

  • Logs that tell a story, not a firehose
  • Metrics shaped around questions you actually ask at 3am
  • Traces that show where a slow request spent its time
  • The cheapest stack that covers all three
  • What to wire up before you ship, what to add after you page

Leave with a blueprint

  • Write logs that let you reconstruct a single request end to end
  • Pick metrics that answer specific production questions
  • Instrument traces across service boundaries without fighting the SDK
  • Stand up logs, metrics, and traces on a free tier
  • Decide what to ship on day one and what to add after the first incident