Metadata to Attach to Error Events for PII-Safe User Incident Tracking

Attach release version, environment, service name, normalized route, request ID, and a stable pseudonymous correlation value to an error event. Omit raw user IDs, emails, access tokens, request bodies, and user-entered text. For the fintech experiment, keep cohort assignment instead of customer identity. If the observability system cannot delete events for a user, treat pre-ingestion redaction as required, not cleanup.

This ensures incident reconstruction, answering questions about specific releases or cohorts without building a shadow customer database. The error field should be included if it alters debugging decisions. The core metadata fields are release version, environment, service name, normalized route, request ID, and stable correlation identifiers.

Add tenant_cohort, experiment_key, and opaque tenant_ref for this experiment. Use route templates, drop raw URLs and query strings, and generate opaque correlation IDs stored separately from the primary controlled store. Invariants include untrusted payloads not deciding observability schema and separation of tenant reference mapping.

Deletion is the hard failure boundary. Consider alternative observability solutions like Sentry, Datadog, or Rollbar if Infrai's deletion and bulk export interfaces are lacking. Geography fields are not compliance controls. Final decision depends on evaluating retention, residency, deletion, and contract terms with privacy and legal owners before selecting an error-tracking vendor.