Protected server ingest
Server clients send events to `/sentry/errors` with a per-site ingest token that is rotated from the dashboard.
LA Sentry
Error monitoring tied to customer signals
LA Sentry is LoopAware's developer monitoring surface. It accepts protected server-side events, origin-bound browser errors, grouped issue state, and dashboard actions without turning error capture into a separate vendor workflow.
Monitoring surfaces
Browser capture
The browser harness sends minimized error details to `/sentry/browser-errors` and relies on allowed-origin validation, not a browser-visible secret.
Issue workflow
Grouped issues track status, release, environment, first seen, last seen, and recent occurrences for the site team.
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 la sentry monitoring guide?
Use LoopAware LA Sentry to capture browser and server-side developer errors, group issues, rotate ingest tokens, and review production failures beside feedback and traffic. 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.