Instrument directory search without capturing query text
Search failure metrics currently include potentially sensitive part queries. Add bounded operational events.
- Focused work estimate
- 2h + prerequisites
- Priority in the scenario
- Low
- Engineering practice
- Instrumentation · Privacy
Estimated field mix
- Privacy engineering60%
- Frontend40%
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
Fictional workshop directory Cedar lists tools and spare parts using a local search adapter.
Setup prerequisites
- Create synthetic items with stable identifiers.
- Stub cursor pages, facets, delayed responses and missing items.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
- CSEARCH-101 · Normalize directory whitespace without changing part codes
- CSEARCH-103 · Announce completed directory searches once
- CSEARCH-102 · Expose selected directory facets in shared links
- CSEARCH-104 · Bind directory page cursors to their originating query
- CSEARCH-107 · Keep zero-count directory facets removable
- CSEARCH-108 · Bound the directory query cache
Acceptance criteria
- Includes outcome and duration bucket
- Omits queries and item names
- Retries retain correlation token
Implementation constraints
- Verify through a local event collector.
Verification to include
- Complete search and inspect event
- Fail secret-like query and check exclusion
Deliverables
- Event allowlist and samples
Rollout and recovery
Disable event sink if unexpected fields appear.
Value of the work
For the engineer: Practice URL contracts and request ownership.
For the team: Inspect whether discovery intent survives changing results.
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.