LoopAware

LA Sentry browser

Browser JavaScript error capture

LoopAware's browser LA Sentry harness captures unhandled errors and rejections through an origin-bound public endpoint so frontend failures can be reviewed beside site feedback and traffic.

Why browser capture is separate

A browser script cannot safely hold a protected server-side token. LoopAware uses a dedicated browser ingest path that validates the configured site ID and allowed origin instead.

<script src="https://loopaware.mprlab.com/la-sentry.js" data-site-id="..."></script>

What it captures

Unhandled errors

Capture runtime JavaScript failures that users may hit in production browsers.

Unhandled rejections

Record failed async paths that otherwise disappear into console noise.

Manual errors

Use the browser harness for explicit `LASentry.captureError` calls when code has known failure boundaries.

Limitations

  • Browser capture does not expose the server-side LA Sentry ingest token.
  • Source map upload and source-map resolution are outside the current repository surface.
  • Private visitor data should not be added to browser error attributes.

Best fit

Use browser capture for public frontend errors that need to be triaged by the same team reviewing site signals.

Implementation checklist

  • Confirm the LoopAware site, browser origin, or protected server ingest token before sending developer errors.
  • Capture one known error and verify the grouped issue includes enough context for triage.
  • Assign owners or team members who will review unresolved, resolved, and ignored issue states.

Common questions

When should teams use this browser error capture guide?

Capture browser JavaScript errors in LoopAware LA Sentry with allowed-origin protection instead of exposing a server-side ingest token. It is useful when developer errors should be reviewed beside site feedback and traffic instead of in a separate monitoring view.

What should teams verify after setup?

Confirm the workflow is tied to the correct LoopAware site, then check the first dashboard records with the people who will act on them.

Logging out...

Logging out...