A report is more than a picture

Console errors, failed requests and environment metadata are collected with the report automatically, so the person fixing it does not have to ask for anything else.

Four kinds of context, captured for you

Collected at submit time, attached to the report, and never monitored in the background.

πŸ“œ

Console errors

Error-level logs and unhandled exceptions, with message and source location (file:line:column).

⚠️

Warnings too

Warning-level output is included when it is the only clue available.

🌐

Failed requests

Requests that return HTTP 400 or above, with method, status and a masked URL.

πŸ–₯️

Environment

Page URL and title, browser and version, operating system, screen size, viewport and pixel ratio.

What never leaves the browser

Diagnostics are useful, but they are also the easiest place to leak something. These safeguards are always on.

βœ‚οΈ

URL masking

Parameters named token, key, secret, password, auth, api_key and similar are replaced with *** before anything is stored.

🎯

One-time collection

Collection happens only at submit β€” there is no background sniffer running on your pages.

πŸ“¦

Bounded buffers

Console entries are capped at 30 and network entries at 20, and only the most recent subset is included.

More from BugCapturer