What belongs in a structured error log for production APIs?
PICTURE THIS: HOW TO EXPLAIN IT
Simple meaning
Request id, route, status, error type, and safe context — never passwords or full cards.
WHY — Observability instead of guessing?
Why interviewers care about Observability:
who only read docs from people who shipped.
and tied to Backend work.
Name the idea, why it exists, then one short example.
End with when you use it and one common pitfall.
STEPS — What happens step by step?
Before you speak the answer, walk the interviewer through these steps:
- 1Request id, route, status,
error type, and safe context — never passwords or full cards.
- 2Correlation ids stitch gateway
and service logs.
- 3How it works
Noise levels stay under control.
- 4Give an example
One tiny concrete case you can say aloud.
- 5Common mistake
What juniors usually get wrong.
- 6Close
When you pick this over the alternative.
EXAMPLE — See it in action
Here's a short line you can speak, broken into clear beats:
Note: Adapt this scaffold to your own project — keep it under 60–90 seconds.
Key takeaway
Request id, route, status, error type, and safe context — never passwords or full cards. Correlation ids stitch gateway and service logs.