A single request-completion record is more valuable than several disconnected “started / controller entered / service entered” lines. Measure elapsed time using a monotonic clock and emit method, normalized route, status, requestId, and duration. const started = performance.now(); try { return await next.handle().toPromise(); } finally { logger.log('HTTP request completed', { requestId, method, route, statusCode, durationMs: Math.round(performance.now() - started), }); }
Metrics worth starting with Metric Type / purpose
http.server.requests Counter - request volume by method/route/status class
http.server.duration Histogram - latency distribution
http.server.active_requests Gauge/up-down counter - current concurrency
taskflow.errors Counter - grouped application error codes
process / runtime CPU, memory, event-loop/runtime signals from platform/instrumentation
Latency dashboards should use percentiles such as p50/p95/p99 rather than averages alone. Histograms are useful because distributions can be aggregated across replicas; averaging precomputed percentiles is statistically wrong. Production caution: Keep metric attributes low-cardinality: method, normalized route, status class, environment. Do not attach requestId or userId to every metric point.
Request Logging and Latency Metrics matters because it changes a real boundary in TaskFlow. The goal is to understand the inputs, owner, observable output, and failure modes before adding more abstraction.
Restate the goal of “Request Logging and Latency Metrics” as one observable behavior. Write the success signal before touching code.
Trace the boundary map: request → correlation id → structured event → metric/trace → diagnosis. Mark the one boundary this lesson changes.
Inspect the current repository state and record the exact files, route, table, or runtime involved. Avoid creating an abstraction before you can name the existing owner.
Implement the smallest vertical slice. Add one coherent change, run the narrowest verification command, and read the output before continuing.
Connect the slice to TaskFlow’s phase artifact: Observability layer connecting Next.js/API errors and request IDs to structured logs and monitoring releases.. Verify behavior from the outside as a user or API client would.
Create one controlled failure that is safe to reproduce. Predict the symptom first, capture evidence, locate the earliest broken boundary, then fix only that cause.
Close the reference and rebuild or explain the core change from memory. Record what you would monitor or test before trusting the same change in production.
logger.error({
requestId, route: request.url, userId: user?.id,
errorCode: error.code, durationMs,
}, "request failed");Do not copy this as a finished answer. Predict what each boundary does, type the smallest useful slice, run it, then compare the result with your prediction.
Return to the nearest observable boundary: input, network, process log, database, or rendered UI. Compare actual evidence with the predicted path.
Change one variable at a time and reproduce the original failure after the fix; otherwise you have correlation, not diagnosis.
Without copying the final source, create a second small scenario that applies “Request Logging and Latency Metrics” to a different TaskFlow resource or input. Write the acceptance criteria first, implement it, and provide the evidence that each criterion is satisfied.
Integrate error monitoring for both Next.js and NestJS and tag releases by commit SHA.
Use the smallest change that demonstrates this lesson. Stop after it works and capture evidence.No release/environment tags so errors cannot be tied to deployments
Predict the symptom before causing the failure. Then locate the earliest boundary where reality diverges from expectation.Why does this responsibility live here, what input does it trust, what output proves success, and what would go wrong if another layer owned it?
If your explanation is vague, repeat the boundary trace before moving on.Close the reference. Reproduce the core idea from memory or explain the exact request/data flow aloud. Then check your diff or notes for accidental shortcuts that bypass validation, authorization, error handling, or verification earned in earlier phases.