Report preview value and cost without vanity counts
A dashboard celebrates total previews created while ignoring failed readiness, time-to-review, idle duration, and leaked resources.
- Focused work estimate
- 2h 30m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Operational metrics · Cost attribution · Responsible analytics
Estimated field mix
- DevOps70%
- Site reliability30%
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 product team creates local preview environments for pull requests. Names collide, fixtures copy more data than needed, failed provisioning leaks resources, and merged changes leave previews running. Build an infrastructure simulator with fake DNS, storage, and deployment providers; no cloud account or live domain is supplied.
Setup prerequisites
- Resource graphs
- Idempotency
- Tenant isolation
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
- DPREVIEW-101 · Derive a collision-resistant preview identity
- DPREVIEW-102 · Compile a minimal preview configuration
- DPREVIEW-103 · Plan the resource graph before creating anything
- DPREVIEW-104 · Apply preview resources idempotently after interruption
- DPREVIEW-105 · Seed representative data without copying customer records
- DPREVIEW-106 · Publish the preview URL only after identity-aware readiness
- DPREVIEW-107 · Enforce preview quotas across concurrent requests
- DPREVIEW-108 · Expire previews without deleting an active replacement
- DPREVIEW-109 · Resume partial preview deletion without losing unresolved resources
Acceptance criteria
- Report creation-to-ready time, ready duration, cleanup latency, failures, and declared resource cost
- Metrics use bounded repository and outcome dimensions
- Unresolved deletion remains included until reconciled
Implementation constraints
- Do not infer developer productivity or individual performance from preview usage.
Verification to include
- Reconcile a mixed fixture cohort from request through deletion.
- Omit cleanup observations and confirm the report shows incomplete cost and lifecycle data.
Deliverables
- Preview lifecycle report and interpretation guide
Rollout and recovery
Use the report to tune lifecycle policy, not rank people.
Value of the work
For the engineer: Practice ephemeral environment lifecycle, scoped configuration, cleanup, quotas, and provider reconciliation.
For the team: Review changes in isolated representative environments while controlling leakage, resource growth, and abandoned infrastructure.
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.