Observability
Understanding system health from the outside — see SYSTEM_DESIGN_ALIGNMENT.md section 9.8.
Why we need this / what value this brings
You can't fix what you can't see — observability is what turns 'something feels slow' into an actionable, specific finding.
When to use this
Build it in alongside the feature, not after the first production incident makes the gap obvious.
How to use or implement this
Start with structured logs and a few key metrics before investing in distributed tracing — match the investment to actual system complexity.
Subtopics
Research questions
- What observability exists today? There's already an Observability-Stack.md doc at the LocalzDocs root worth reading first.
Empty folder — drop notes, links, and findings here as you research.