Manuals / Observability Basics / Chapter 2

A · Pillars · beginner · Week 1 · Chapter 2 of 9

Logs that help

Structured logs beat string soup. Correlation IDs stitch requests. Levels matter. PII doesn’t belong.

Path progress
22%

Step 1 of 1

Trace one request in logs

  • Timestamp range
  • Service name
  • Correlation / trace id
  • Error fields
Trace one request in logsDrag stickies · tap for tips
Study mapDrag stickies · tap for tipsKeep it shortdrag · tap →Name the waitdrag · tap →Scope locatorsdrag · tap →Trace when stuckdrag · tap →One browser firstdrag · tap →Isolate statedrag · tap →Assert the UIdrag · tap →Retry wiselydrag · tap →Seed datadrag · tap →Close the loopdrag · tap →Keep it shortdrag · tap →Name the waitdrag · tap →Scope locatorsdrag · tap →Trace when stuckdrag · tap →One browser firstdrag · tap →Isolate statedrag · tap →Pathwise hackdrag · tap →Trace one request drag · tap →Try thisdrag · tap →Follow the dashed drag · tap →

Do this now

Reproduce a flow in staging. Copy a request/correlation id. Find all related lines.

Was this step clear?
Chapter learning outcomes
  • Structured logging
  • Correlation IDs
  • Query patterns

Clear these before you leave