Separate arrival rate from successful service rate
The dashboard counts retries as new incoming customer work.
- Focused work estimate
- 2h + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Metrics · Capacity analysis
Estimated field mix
- Site reliability60%
- Performance engineering40%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Review it, then add it to your workspace.
The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.
Project context
A fictional document service has a rising processing backlog. Operators cannot tell whether arrivals, worker failures, or a slow dependency is responsible.
Setup prerequisites
- Create a bounded local queue simulation with synthetic jobs and controllable worker/dependency failures.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Track logical arrivals, attempts, and completions separately.
- Use consistent measurement windows.
- Expose worker concurrency with throughput.
Implementation constraints
- Do not infer capacity from a single peak sample.
Verification to include
- Reconcile a fixture with repeated attempts.
- Detect growing backlog despite high attempt throughput.
Deliverables
- Queue flow dashboard.
Rollout and recovery
Compare against synthetic queue inventory before relying on alerts.
Value of the work
For the engineer: Practice incident timelines, queue diagnosis, and measured recovery.
For the team: Produce a repeatable response that preserves work integrity and exposes customer delay.
Evidence boundaries
Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.
Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.