Rotate a token
Owner/admin users rotate and reveal a per-site LA Sentry ingest token from the dashboard. Tokens are shown once and intended for server-side clients.
Server-side errors
Server-side error capture for Go and Python services
LoopAware LA Sentry accepts protected server-side error events at `/sentry/errors`. The repository includes first-party Go and Python clients so backend services can send exceptions, tags, environment, release, and request context into grouped dashboard issues.
The problem
Production failures are easier to prioritize when operators can compare them with feedback, traffic, and health state for the same site. Server-side LA Sentry events keep backend exceptions in that LoopAware context without exposing ingest tokens to browsers.
Authorization: Bearer YOUR_SERVER_SIDE_TOKEN
POST /sentry/errorsHow it works
Install a client
Use `clients/go/lasentry` or `clients/python/la_sentry` to send service errors to the protected ingest endpoint.
Review grouped issues
Site teams inspect grouped issues with status, release, environment, latest occurrence, and recent occurrences.
Feature-to-benefit fit
Server-only token
Keeps protected ingest credentials out of browser JavaScript and separates server capture from origin-bound browser capture.
Middleware helpers
The Go client can wrap HTTP handlers, while the Python client includes WSGI and ASGI middleware helpers.
Issue status
Operators can mark issues unresolved, resolved, or ignored as they triage production failures.
Use-case examples
Go API panic capture
Wrap a Go HTTP handler so panics are captured before a 500 response is returned.
Python service exceptions
Send caught exceptions with tags such as service name, queue, release, or environment.
Self-hosted operations
Run feedback, traffic, health checks, and backend error capture in the same source-available deployment.
Objections and limitations
- Server-side clients require an ingest token. Do not embed that token in browser JavaScript.
- LoopAware currently documents first-party Go and Python clients plus the browser harness. Node.js, Ruby, PHP, Java/Kotlin, and .NET clients are not current shipped clients.
- LA Sentry is LoopAware's developer monitoring surface; do not treat it as a full customer-support or ticketing workflow.
For browser JavaScript events without a server token, use the LA Sentry browser capture path.
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 server side error capture guide?
Capture Go and Python server errors with LoopAware LA Sentry clients, protected ingest tokens, middleware helpers, grouped issues, and dashboard review. 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.
Keep backend failures in the site context
When production errors affect the same site that collects feedback and traffic, review them in the same LoopAware operator surface.