vault / systems / observability.md

Observability

System design 51 words 3 outgoing 5 backlinks

For feedback investigation, record enough of the request to reconstruct what happened: the question, retrieval, response and relevant configuration. A trace helps connect those steps. Dashboards can show a pattern, but a concrete replay is often what tells us which component or document needs attention.

Read the full example: related post.

LINKS IN THIS NOTE

[[ Distributed traces ]] A trace follows a request through the services and steps it touches. It lets a slow or failed prediction be inspected as one chain rather than unrelated log lines. In a serving interface, tracing is useful as a shared platform... [[ P95 latency ]] P95 describes the point below which 95% of measured request times fall. It says more about slow requests than an average, but still needs a workload and measurement window. A load-test result is not a promise about production traffic. Bounded... [[ Feedback triage ]] A thumbs-down starts an investigation, not a diagnosis. The workflow I built replays the question, collects evidence, distinguishes a content gap from a configuration issue, and routes the case to an owner. Routing is ordinary code; the model proposes the...