π‘ Live Logs & Error Monitoring
Automatically detect JavaScript errors, failed API calls, and crashes on your website β captured with full diagnostic context and synced to your workflow.
π Overview#
Live Logs is Snifferβs built-in error monitoring system. Once the Sniffer script tag is installed on your website, it passively monitors for JavaScript errors, unhandled promise rejections, failed network requests, and resource load failures. Detected errors are captured with full context and logged automatically in your project as System Bugs.
Unlike standalone error monitoring tools, Live Logs is fully integrated into Snifferβs defect tracking pipeline. Detected errors can automatically become issues on your π Task BoardΒ , get assigned to developers, and sync to π JiraΒ β all without manual intervention.
For details on the System Bug list and detail view, see π°οΈ System Bugs βΒ . For the CDN-driven capture flow, see π€ Sniffer AutoBug βΒ .
πΌοΈ Insert image of the Live Logs dashboard showing a live stream of incoming errors.
π Getting Started#
Prerequisites#
The Sniffer script tag must be installed on your website:
<script
src="https://cdn.snifferweb.com/sniffer.js"
data-project-id="YOUR_PROJECT_ID"
></script>Tip: This is the same script that powers the π¬ Feedback WidgetΒ and π€ Sniffer AutoBugΒ . One snippet, three features.
βοΈ Enable Error Monitoring#
- Navigate to βοΈ SettingsΒ within your project.
- Enable the Live Logs toggle (
isLiveLogEnabledflag). - Configure capture settings and alert thresholds.
- Ensure your domain is in the Whitelisted URLs list (π’ Company SettingsΒ ).
π What Gets Captured#
π± Device Context (Auto-Captured)#
Every error includes:
π System Bug List#
Route: /sf/projects/:id/system-bugs
All auto-detected errors appear in a filterable list. See π°οΈ System Bugs βΒ for the full UI walkthrough.
πΌοΈ Insert image of the System Bug list with severity, count, and last-seen columns.
π System Bug Detail View#
Route: /sf/projects/:id/system-bugs/:bugId
Click any error to open the detail view with these tabs:
1. βΉοΈ Info Tab#
2. π Console Logs Tab#
Shows the first 30 log entries. Logs are filterable by level.
3. π Network Logs Tab#
Shows the first 30 network entries with error highlighting.
4. π¬ Comments Tab#
Team discussion about the error β same comment features as π Bug DetailsΒ .
5. π Linked Tasks Tab#
Link the system bug to related issues on the π Task BoardΒ . Useful when one error has multiple fix-tasks or is being investigated as part of a broader story.
πΌοΈ Insert image of the System Bug detail view with all 5 tabs visible.
βοΈ Configuration#
π Live Logs Documentation#
For Support organization projects, a Live Logs Docs page is available in the sidebar under Settings. It provides:
- Step-by-step script installation guide (with framework examples for React, Vue, Angular, Next.js)
- Domain whitelisting instructions
- Configuration best practices
- Source-map upload guide
- Troubleshooting tips
π Integration with Task Board#
Auto-detected errors that become issues appear on the π Task BoardΒ with:
- Source indicator: System bug icon distinguishes them from manual bugs
- Platform field: Set to the detected platform
- Attachments: Console logs, network logs, and device context attached automatically
- Jira sync: If π Jira integrationΒ is active, auto-detected issues sync to Jira
- Affected Files (AI): Auto-suggested file list based on stack trace + repo integration
π Live Feed (Real-Time Stream)#
A WebSocket-backed live feed displays errors as they happen:
- New errors flow in at the top
- Click-through to detail view
- Pause / resume button
- Filter by URL, error type, severity