A dashboard should answer an operational question. A good first TaskFlow dashboard focuses on traffic, errors, latency, and saturation/health rather than decorative charts.
Request rate Is traffic normal?
5xx / error-code rate Are users failing?
p50 / p95 / p99 latency How slow is the experience, including tail latency?
Readiness / instance count Can healthy replicas serve traffic?
DB/connection/runtime saturation Is a constrained resource causing the symptom?
Release marker Did behavior change after a deploy?
Alert on symptoms first • High user-visible error rate for a sustained window.
• p95 latency over a meaningful threshold for a sustained window.
• No ready instances / repeated readiness failure.
• Critical background workflow repeatedly failing.
• Security/abuse alerts with clear actionability. Production caution: Avoid alerts like “one exception occurred” or “CPU hit 71% once.” Alerts that constantly fire without requiring action train engineers to ignore them.
Authentication answers who the request represents. Treating decoded or client-supplied identity as trusted is a security boundary failure.
Restate the goal of “Dashboards SLOs and Alert Design” as one observable behavior. Write the success signal before touching code.
Trace the boundary map: credentials/session → token → verification → trusted identity → protected operation. 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.
const token = readBearerToken(request);
const claims = await verifier.verify(token);
request.user = {
id: claims.sub,
email: claims.email,
};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.
Inspect whether a token exists, whether it is expired, which issuer/audience signed it, and what the API verifier expects.
Trust only verified server claims; never repair identity by accepting a client-sent user id.
Without copying the final source, create a second small scenario that applies “Dashboards SLOs and Alert Design” to a different TaskFlow resource or input. Write the acceptance criteria first, implement it, and provide the evidence that each criterion is satisfied.
Redact secrets and PII deliberately before adding rich context.
Use the smallest change that demonstrates this lesson. Stop after it works and capture evidence.console.log strings with no searchable structure
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.