Errova helps you capture errors, messages, and logs from browser and server runtimes without giving up security, useful metadata, or control over noisy traffic. These docs are organized around the decisions teams usually make during rollout: which package to install, which key type to use, how to verify the first event, and how to keep the data you send clear and safe.
Recommended Starting Paths
- First production rollout: Getting Started
- JavaScript or TypeScript apps: JavaScript SDKs and Support Tiers
- Python services: Python Setup
- Custom runtimes or centralized pipelines: Direct Ingest API
- Security model first: DSN Keys and Signed Ingest
What Good Setup Looks Like
- Events land under the correct project and environment on the first try.
- Every event carries stable
environmentandreleasemetadata. - Browser traffic is protected with allowed origins, or backend traffic is signed.
- Issues group cleanly because messages, stack traces, and fingerprints are stable.
- Duplicate storms are controlled with SDK burst guard settings and alerting.
Core Terms
- Organization: your workspace for projects, members, alerts, and billing.
- Project: the app or service that receives events, DSN keys, and filters.
- DSN key: the credential pair used for ingest. Choose either browser-public or server-signed.
- Machine token: bearer token for automation against management API routes.
- Environment / release: metadata that makes filtering, trends, and rollout comparison useful.
Recommended Rollout Order
- Create an organization and project.
- Choose the DSN key type that matches the runtime.
- Install the SDK package that matches the framework, or use direct ingest if no SDK fits.
- Send one test error and verify it arrives before adding more instrumentation.
- Attach
environment,release, tags, and user context. - Lock down production with origin enforcement or server signing.
- Configure alerts and burst guard behavior after the baseline signal looks healthy.