How would you monitor this system?
Practice this questionDiscussion template: use your own project facts, ownership, and measured outcomes. Bracketed text is a placeholder.
Short explanation:
Monitoring tracks whether the system meets its operational goals and helps locate failures. Metrics show trends, logs show events and traces connect steps in a request or workflow. Useful monitoring includes business progress, not just whether processes are alive.
Key points:
-
Track latency, errors, traffic, CPU/memory, DB waits and queue age.
-
Connect logs with request/workflow IDs and alert on user impact.
-
For a workflow, measure oldest pending run, failed step rate and provider latency alongside CPU and memory.
Interview point:
- Explain which alert would indicate user impact and what evidence would guide the first investigation step.
Adapted from 10_RESUME_PROJECT_DEEP_DIVE.md · “How would you monitor this system?”. Code examples are study fragments. Difficulty and core labels are editorial estimates; version-specific behavior should be checked against your project.