Console Logs
Configure browser console capture so bug tickets include errors, warnings, failed requests, and useful debugging context.
NOCK can attach browser console context to widget tickets. This helps developers see client-side failures without asking the reporter to open DevTools.
Configure it in Settings > Console.
What NOCK captures
The widget installs a small ring buffer while it is loaded. At submission time, the current buffer is attached to the ticket.
| Source | Captured as |
|---|---|
console.error(...) | error |
console.warn(...) | warn |
console.log(...) | log |
| Unhandled JavaScript errors | error, with stack when available |
| Unhandled promise rejections | error, with stack when available |
Failed fetch requests | error, including method, URL, status, or network failure |
NOCK skips its own /api/widget/ calls so widget internals do not pollute your app's debugging context.
Log levels
| Setting | Captures |
|---|---|
| Error only | Errors, unhandled exceptions, unhandled rejections, failed network requests |
| Warn and above | Error-level entries plus console.warn(...) |
| Info and above | Warn and error entries plus console.log(...) |
| All levels | Same capture set as info today; reserved for fuller verbose capture later |
Start with Error only or Warn and above. Move to broader capture only when your app logs useful structured context.
Exclude patterns
In Settings > Console, add up to 20 exclude patterns. Each pattern is compiled as a JavaScript regular expression and matched against the rendered log message.
Use patterns to drop noisy or sensitive messages before they are stored on a ticket.
^Heartbeat
analytics
ResizeObserver loop limit exceededInvalid regex patterns are ignored by the widget.
Max entries
The Dashboard accepts a max-entry value from 0 to 100. The widget keeps a ring buffer and stores the most recent entries.
Note
The runtime clamps the buffer to at least one entry. Use a narrow log level and exclude patterns when you want minimal capture.
Privacy
Console logs can contain anything your application writes to the browser console. Before enabling broad capture, make sure production logs do not include passwords, API tokens, payment data, or personal information that your team does not need for debugging.
Captured logs are stored with the ticket and are visible to team members who can view that ticket.