Features
A trace is one operation from start to finish; a span is one timed step inside it. Buglapse builds traces automatically for page loads, navigations and HTTP requests, and lets you time your own code in one call.
Tracing
Every span with its duration, parent, operation and status, laid out on a timeline — the slow step is visible without reading a single log.
In the browser a span opens for the initial page load and for every route change, with fetch requests under it. In Node.js each incoming request is a root span and outgoing HTTP calls are recorded.
A request that starts in the browser and continues in your Node.js server is shown as one trace, so the frontend and the backend part of a slow page sit side by side.
Attach named numbers to a span — rows imported, payload bytes, order total — and see them charted on the trace page. They cost nothing beyond the span itself.
How it works
Browser tracing and the Node.js HTTP integrations create spans for page loads, navigations and requests without any changes to your code.
Put a step into span or asyncSpan. It is timed and sent when the callback returns, resolves or throws; a span that throws is marked as failed.
Find the trace by name, duration or status and read the waterfall. Errors and logs captured during the operation are linked to it.
import { asyncSpan } from '@buglapse/node'
await asyncSpan('checkout', async () => {
await asyncSpan('reserve-stock', () => reserve(cart))
await asyncSpan('charge-card', () => charge(cart))
})In detail
There is no separate call to start a trace: the first span with no active parent becomes the root of a new one. A span started inside another becomes its child automatically. In Node.js the active span follows the asynchronous call chain, so concurrent requests each build their own tree and never see each other's spans. For work that overlaps in time, such as parallel requests, a leaf span that you end yourself keeps the tree correct.
Anything that is not an incoming HTTP request becomes a trace as soon as you wrap it in a root span: a queue job, a cron run, a migration script. Every span can carry a status, extra data and metrics, so a trace of an import job can show how many rows it handled and where it stalled.
| Free | Pro | Team | |
|---|---|---|---|
| Spans / month | 100,000 | 1,000,000 | 10,000,000 |
| Traces | 7 days | 14 days | 30 days |
FAQ
Still have questions?
Drop us a line — we'll help with setup, plans or self-hosting.
Contact usor email hello@buglapse.com
See also
Structured logs next to errors and traces, searchable by message, level and attribute.
Learn more: LogsEvery error grouped into one issue with a readable stack trace, breadcrumbs, the steps to the error and the affected users.
Learn more: Error trackingErrors, request traces, logs and event loop stalls from your Node.js server.
Learn more: Node.jsCreate a project on the free plan and send your first event in a couple of minutes.
Still have questions? Email hello@buglapse.com