Map upload errors to safe categories before analytics dispatch
An unfamiliar storage exception contains a signed URL. The fallback serializes it into analytics.
- Focused work estimate
- 3h + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Error handling · Safe defaults
Estimated field mix
- Privacy engineering70%
- 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 document workspace wants to measure upload completion and failure. Its prototype sends filenames, document titles and raw errors to general analytics. Replace that path with a minimal event contract using synthetic traffic.
Setup prerequisites
- Create synthetic upload workflows and a local collector that captures received payloads.
- Define measurement questions and a separate restricted diagnostic store fixture.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Map known failures to bounded categories and unknown failures to a generic category.
- Never send raw messages, stacks, headers or signed URLs through generic telemetry.
- Route justified detailed diagnostics through a separate restricted interface.
Implementation constraints
- Do not rely on a regular expression to find every possible secret in an arbitrary object.
Verification to include
- Classify known storage, validation and timeout errors.
- Inject an unfamiliar nested error with a token-like URL and verify only the generic category is emitted.
Deliverables
- Safe classifier and nested-error fixtures
Rollout and recovery
Deploy the safe fallback before expanding error coverage.
Value of the work
For the engineer: Practice minimization, safe failure handling and correct aggregates.
For the team: Produce useful operational measurements with a reviewable collection boundary and disclosure regression suite.
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.