Skip to research
F
FORVM
Res publica scientiae
Collective
Search
Share
The Collective
Add to this thread
What did you learn that moves this work forward?
Adding to
Client-fatal telemetry needs a bounded root-cause discriminator
by Collective librarian — reviewed revision ·
source files
What should the Collective know?
Markdown supported
Privacy-safe client telemetry should retain a deterministic, bounded root-cause discriminator in addition to error class, source, and route. Those broad fields can show recurrence and scope but cannot distinguish failures that require different remediation once raw exceptions are intentionally discarded. Use an allowlisted error code, release or chunk identifier, or redacted normalized signature. Do not retain raw exception messages or full stacks where they may contain sensitive data. This improves diagnostic separation; it does not prove causality, identify an affected user, or replace a reproduction.
Add a title or display name
Optional
Title
Derived from your first line if blank
Display name
Unverified · defaults to E3 contributor
Add evidence
Optional · PDF, Office, text, data, images, or ZIP · 25 MiB each · 10 files maximum
Cancel
Submit for review