Buglapse collects what goes wrong in your application — errors, logs, traces, metrics, page views and session replays — and turns it into issues you can triage, search, and hand off to an AI agent for a fix. Data gets there through an SDK you add to your app; everything else happens in the dashboard.

Pick an SDK

SDK	Package	Runs in	Start here
Browser	@buglapse/browser or a script tag	The page: errors, logs, traces, metrics, hits, session replay	Browser quickstart
Node	@buglapse/node	A Node.js process: API servers, queue workers, cron scripts	Node quickstart

Every project is identified by its DSN — https://{key}@{host}, shown on the project's Settings → General tab. The script-tag install snippet, with the DSN already baked in, is on Settings → Loader Script.

How data flows

1. The SDK captures something — an uncaught error, a log.info() call, a finished span — and turns it into an event.
2. Events are batched and sent to https://app.buglapse.com/api/envelope by a transport.
3. The server stores each event by type: exceptions are grouped into issues, spans build traces, logs and hits become searchable rows.
4. In the dashboard you filter everything with one search syntax, decode minified stacks with source maps, and let Autofix propose a fix. AI clients can reach the same data through the MCP server.

Reference

• Events — the envelope format and every event type the SDKs send.
• Issues — grouping, fingerprints, triage.
• Search — the query language used by every list in the dashboard.