🛰️ System Bugs

The list and detail view for auto-detected production errors captured by 📡 Live Logs and 🤖 Sniffer AutoBug .

🌟 Overview#

While the 📋 Task Board is where humans triage manually-reported bugs, System Bugs is where machine-detected errors live — the JavaScript exceptions, failed API calls, unhandled rejections, and resource failures captured automatically from your live website.

Each system bug is deduplicated by fingerprint, includes an occurrence count, affected-user count, first/last-seen timestamps, and the full diagnostic context. From here, engineers triage errors, link them to fix tasks, and resolve them.

System Bugs and the regular Task Board can be linked together — a recurring system error can be linked to the engineering ticket assigned to fix it, and closing the engineering ticket can auto-resolve the system bug.

🖼️ Insert image of the System Bugs list page with several errors, severity chips, and occurrence counts.

Routes:

List → /sf/projects/:id/system-bugs
Detail → /sf/projects/:id/system-bugs/:bugId

📋 List View#

The list view is the triage workspace.

Columns#

Column	Description
Error Message	Truncated error text — full text on hover
Type	`JS Error`, `Network`, `Promise Rejection`, `Resource`, `CSP`
Severity	Auto-assigned (Critical, High, Medium, Low)
Status	New, Investigating, Resolved, Ignored
Count	Occurrences (deduplicated by fingerprint)
Users	Distinct users impacted
First Seen	Initial detection timestamp
Last Seen	Most recent occurrence
Affected URLs	Pages where the error occurred (top 3 + count)
Linked Task	Linked Task Board issue, if any
Actions	Investigate · Resolve · Ignore · Link · Delete

Filters#

Filter	Options
Status	New, Investigating, Resolved, Ignored
Severity	Critical, High, Medium, Low
Type	JS Error / Network / Promise / Resource / CSP
URL	Match by URL pattern
Browser	Chrome, Firefox, Safari, Edge
OS	macOS, Windows, iOS, Android
First Seen	Date range
Last Seen	Date range
Search	Free-text in message or stack trace

Bulk Actions#

Mark as Resolved (with optional resolution note)
Mark as Ignored (won’t generate alerts)
Link to Task — link multiple system bugs to one engineering ticket
Assign Severity — bulk re-classify
Delete

🐛 System Bug Detail#

Click any error to open the detail view with five tabs:

1. ℹ️ Info Tab#

🖼️ Insert image of the Info tab with stack trace and metadata.

Field	Description
Error Message	Full error text
Stack Trace	Complete JS stack trace, source-mapped if maps are present
Error Type	Classification
Fingerprint	Hash used for deduplication
Occurrence Count	How many times this error has fired
Affected Users	Distinct user IDs / sessions
Affected URLs	Pages where it occurred
First / Last Seen	Timestamps
Environment	Dev / Staging / Prod
Linked Bug	If converted to a Task Board issue, link to it

2. 📟 Console Logs Tab#

The first 30 console entries captured around the time of the error. Color-coded by level, searchable. See 📡 Live Logs for details.

3. 🌐 Network Logs Tab#

The first 30 network entries with error highlighting. Bodies and headers expandable.

4. 💬 Comments Tab#

Team discussion about the error. Same comment features as the 🐛 Bug Details drawer — @mentions, threads, edit/delete.

5. 🔗 Linked Tasks Tab#

Action	Description
➕ Link existing	Search and link a Task Board issue
➕ Create from this	Spawn a new Task Board issue pre-populated with all context
🔓 Unlink	Remove a link

🖼️ Insert image of the Linked Tasks tab showing one linked engineering ticket.

🔄 Status Lifecycle#


🆕 New → 🔍 Investigating → ✅ Resolved
                          → 🚫 Ignored

Status	Effect
New	Default state for fresh errors. Counted in dashboards.
Investigating	Set when an engineer picks it up; counted as in-progress.
Resolved	Marked fixed. Future occurrences re-open it.
Ignored	Won’t generate alerts even if it recurs. Useful for 3rd-party noise.

🚨 Alerting#

When a new system bug is detected (or an existing one passes a threshold), Sniffer can:

🔔 Send an in-app notification
📧 Email project members
🦊 Post to a Slack / Teams channel
🎫 Auto-create a 📋 Task Board issue if Auto-Create Issues is enabled in 📡 Live Logs config

Thresholds (configured per project):

Threshold	Behaviour
Immediate	Alert on first occurrence
3+ count	Alert after the 3rd occurrence
10+ count	Alert after 10 occurrences
Burst rate	Alert when N occurrences happen within M minutes

🤖 AI on System Bugs#

The 🤖 AI Analysis tab is available on system bugs too:

Root cause inference from stack trace + network context
Affected file suggestions (if GitHub/Bitbucket is linked)
Reproduction steps based on action timeline
Related bug suggestions

🔐 Permissions#

Action	Required Permission
📡 View system bugs	`LIVE_LOGS.VIEW`
⚙️ Resolve / Ignore	`LIVE_LOGS.CONFIGURE`
🔗 Link to Task Board	`TASK_BOARD.EDIT`

Topic	Description
📡 Live Logs →	The error monitoring pipeline
🤖 Sniffer AutoBug →	CDN-driven auto-capture
📋 Task Board →	Convert system bugs to engineering issues
🐛 Bug Details →	Detail drawer for human-reported bugs
📊 Dashboard →	System-bug metrics
🧩 Sniffer for Jira →	System bug context inside Jira
🤖 Ask AI →	Chat with the AI about an open system bug