Identify groups that began firing after a deploy or release.
- Resolve
$ARGUMENTSto an ISO 8601 timestamp.- If the user gave an ISO timestamp, use it directly.
- If they gave a relative phrase (
30m ago,2h ago,yesterday at 3pm), convert it. - If they gave nothing, ask: what's the deploy timestamp or commit time?
- Call
list_error_groupswithsince: <timestamp>and the default limit. - Filter the response to groups where
first_seen_at >= <timestamp>— these are new groups, not just groups that were also hit before the deploy. This is the regression signal. - Render:
id | exception_class | message | first_seen_at | occurrences_count. Sort byfirst_seen_atascending so the earliest regression is first. - If any candidates are found, suggest investigating the earliest one with
/debug <id>— its backtrace will point at the code introduced by the deploy.
If the result is empty, the deploy looks clean from Faultline's perspective. Mention that errors filtered by ignored_exceptions won't show up here either.
Source: dlt/faultline — distributed by TomeVault.