Features
Send log lines with a level and structured attributes from the browser and from Node.js. They land next to the errors and traces of the same project, with the same release, environment and user.
Logs
Keep the message a fixed, readable string and put the variable parts into attributes. Every top-level attribute becomes a search filter in the dashboard.
Turn on the console integration and existing console.log, info, warn, error and debug calls are forwarded as logs. The original output in DevTools stays unchanged.
Filter the Logs page by message, level, attribute, release, environment or user, with the same search syntax as the rest of the dashboard.
A log written while a request or a page load is being traced belongs to that trace, so you can jump from a line to the whole operation around it.
How it works
The log API is part of the browser and Node.js packages — there is nothing extra to install once init has been called.
Call log.info, log.warn or log.error with a message and an object of attributes. Logs are batched and sent together with the other events.
Open Logs in the project, filter by level or by any attribute you sent, and open the related trace when a line needs more context.
import { log } from '@buglapse/browser'
log.info('Order placed', { orderId: 1042, total: 59.9 })
log.warn('Payment retry', { orderId: 1042, attempt: 2 })In detail
A log is one line of text with a level and an optional set of attributes. Attributes belong to that single line, while tags, context and the user set on the SDK are attached to everything sent afterwards. Use attributes for what happened in this call, and tags or context for who and where. Flat objects with string, number or boolean values work best: nested objects are stored and shown, but are not offered as filters.
A line logged at the error level is still a log: it is searchable and counted as a log, but it does not create an issue. To get grouping, a stack trace and alerts, report the exception itself. In Node.js, the event loop integration also writes a warning log whenever synchronous code blocks the process for too long — a problem that never throws an error on its own.
| Free | Pro | Team | |
|---|---|---|---|
| Logs / month | 50,000 | 500,000 | 5,000,000 |
| Logs | 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
Every error grouped into one issue with a readable stack trace, breadcrumbs, the steps to the error and the affected users.
Learn more: Error trackingLet Claude Code, Cursor and other AI assistants read your issues, traces and logs.
Learn more: MCP serverCreate a project on the free plan and send your first event in a couple of minutes.
Still have questions? Email hello@buglapse.com