Introduction
Understand what Reelay does, how the pieces fit together, and where to start.
What is Reelay?
Reelay helps you check code before release and investigate errors after release. Connect GitHub to scan a repository. Add an SDK to capture errors and the requests or user activity around them. You can use these workflows separately or together.
When an error needs a coordinated response, link it to an incident. The incident keeps the owner, investigation, updates, and follow-up work in one place. AI analysis can help explain a likely cause and suggest changes for your team to review.
Why use it?
A stack trace tells you where an error surfaced. You may still need to find the failed request, the user's actions, the deployed code, and the team responsible. Reelay connects captured evidence so you can investigate the same failure instead of collecting each piece again.
Code scanning gives you an earlier opportunity to review security and quality findings. Scans and AI suggestions support engineering judgment; they do not prove a release is free of bugs.
How it works
| Part | What it does |
|---|---|
| Workspace | Holds your team's environments, integrations, members, and billing. |
| Environment | Separates production, staging, and other deployments. |
| Node | Identifies an application, backend service, or worker sending telemetry. |
| Error event and group | An event is one occurrence. A group collects related occurrences for triage. |
| Incident | Tracks an active response, its owner, updates, and resolution. |
| Repository and commit | Give scans and source-aware analysis the code revision to inspect. |
| Enterprise Agent | Receives telemetry and runs private scans and analysis in your infrastructure. |
Choose your starting point
Before you send production data
Start in staging. Confirm the right environment, node, and deployed commit are attached to a test event. Review masking and filtering against your own application data, then decide which errors and performance events to sample.