owl24-web

Browser Real User Monitoring (RUM) SDK for owl24 — one function call to send Core Web Vitals, page-load timing, and uncaught JS errors from your frontend to your owl24 dashboard.

Install

npm install owl24-web

Usage

import { Owl24Web } from 'owl24-web';

Owl24Web.init('YOUR_API_KEY', { serviceName: 'my-frontend' });

Call init() as early as possible in your app's entry point, before your router or component tree mounts — Web Vitals like LCP and FCP are measured from page load, so initializing late can miss or under-report them.

That's it. Core Web Vitals (LCP, CLS, INP, FCP, TTFB), a page-load span, and uncaught JS errors/unhandled promise rejections are all captured automatically the moment init() runs — no separate error-boundary setup, no extra wiring.

What gets sent

• Core Web Vitals — LCP, CLS, INP, FCP, TTFB, via the web-vitals library.
• A page-load span — navigation timing for the current page view.
• Uncaught errors — window.onerror and unhandledrejection, unless you pass disableErrorCapture: true.

This SDK has no request/response bodies to scan the way the server SDKs do — what it captures instead is page URLs (query strings and all), Core Web Vitals, and browser/error context. A page URL with an identifier or search term in it isn't a card number or an IBAN, so the masking below won't catch it — if your app puts sensitive data in URLs, that's worth knowing before you enable this.

PII masking

Runs the same masking logic as the other four owl24 SDKs — emails, credit-card-shaped numbers, phone numbers, and bearer tokens are scrubbed before anything leaves the browser, on by default, no config needed. Pass maskFields to add your own field names to the default list.

Working with your coding agent

Errors captured via this SDK can be deduplicated and handed straight to your own coding agent - claim, investigate, fix, PR. Reach that queue interactively from Claude Code or Cursor with owl24-mcp, or unattended via REST + AGENTS.md (see the docs).

License

MIT — see LICENSE.