Improve SigNoz exception taxonomy, tags, and redaction #74

Closed
opened 2026-08-01 23:39:47 +00:00 by coilyco-ops · 0 comments
Member

The catch-all SigNoz exception baseline is now landed and deployed. This issue improves the projection without reducing coverage.

Scope:

  • Define a stable, low-cardinality exception taxonomy for grouping and alerting.
  • Improve human-readable wording while keeping messages closed-set and body-free.
  • Add only bounded, operationally useful tags such as error stage or outcome.
  • Audit exception messages, stack traces, span attributes, and status descriptions for redaction.
  • Preserve an exception event for every handled and background runtime failure.
  • Add regression tests proving dynamic upstream, request, user, path, credential, and payload data cannot enter exception fields.

Acceptance:

  • Every existing baseline error path still emits an exception event.
  • Grouping cardinality is bounded and documented.
  • Live verification records one safe representative error in SigNoz after rollout.

Baseline: d6e9d10c7c286206296cf52b140ad92ea3b4cbef.

The catch-all SigNoz exception baseline is now landed and deployed. This issue improves the projection without reducing coverage. Scope: * Define a stable, low-cardinality exception taxonomy for grouping and alerting. * Improve human-readable wording while keeping messages closed-set and body-free. * Add only bounded, operationally useful tags such as error stage or outcome. * Audit exception messages, stack traces, span attributes, and status descriptions for redaction. * Preserve an exception event for every handled and background runtime failure. * Add regression tests proving dynamic upstream, request, user, path, credential, and payload data cannot enter exception fields. Acceptance: * Every existing baseline error path still emits an exception event. * Grouping cardinality is bounded and documented. * Live verification records one safe representative error in SigNoz after rollout. Baseline: `d6e9d10c7c286206296cf52b140ad92ea3b4cbef`.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
coilyco-flight-deck/agent-proxy#74
No description provided.