One page per language, so you never scroll past a stack that is not yours. Every SDK shares one contract: batched shipping that never blocks your request path, errors reported with the stack and the log trail, and the same privacy rule — request bodies, headers, cookies and query strings are never captured.
Every SDK is open source under MIT, at github.com/InsightRecorder. Read what an agent running inside your application actually does before you install it — that is the point of shipping the source, and of keeping every one of them free of third-party runtime dependencies.
Every SDK takes a base URL (INSIGHT_BASE_URL): the address of your InsightRecorder deployment — the server that receives your data — not the application you are monitoring, which is where the SDK runs. Self-hosted, it is your own instance (e.g. https://insight.yourcompany.com); on the hosted service it is your InsightRecorder host.
Capture the session that produced the bug. The agent is the front door; the adapters exist because React and Vue intercept component errors before the agent can see them.
One script tag captures console, network timing and user steps — and transmits nothing until a report is triggered.
capture.js (script tag)Error boundaries swallow render errors before window.onerror ever sees them. This closes that gap and attaches the component stack.
@insightrecorder/capture-reactVue routes component errors to app.config.errorHandler, never to window.onerror. The plugin closes that gap and names the failing component and hook.
@insightrecorder/capture-vueShip logs and turn errors into bug reports. No third-party runtime dependency in any of them.
Ship logs, turn panics into bug reports with the stack and the log trail, and query the API.
github.com/InsightRecorder/insight-recorder-goBatched log shipping plus an Express error handler that attaches the log lines leading to the failure.
@insightrecorder/insight-recorderA logging.Handler you add alongside the existing ones, plus WSGI middleware for Django and Flask.
insight-recorderBroadcast your Rails logger and insert one Rack middleware — which re-raises, so rescue_from and your error pages still run.
insight_recorderThe one SDK that breaks the shape: PHP has no background threads, so it buffers and flushes at end of request — after the response has already reached the browser.
insightrecorder/insight-recorderHTTP is java.net.http and JSON is internal, so the SDK cannot collide with the Jackson version your application pins.
com.insightrecorder.insightHttpClient and System.Text.Json ship with the framework, so nothing collides with what your application pins.
InsightRecorder.InsightHTTP comes from OTP (:httpc), so the SDK adds no HTTP client to your dependency tree.
:insight_recorderLooking for the endpoints instead? The full API reference is at /docs, and the source for every SDK is on GitHub.