Quickstart
Set up a workspace, connect your application, and verify your first event.
1. Create a workspace
Create an account and use the workspace where your team will manage the application. Invite teammates who need to investigate or respond. A workspace keeps integrations, events, and billing together.
2. Add an environment and node
Open Environments and create a stable name such as staging or production.
Open Nodes and create a node for the application or service. Select its environment and associate its repository when you need source-aware analysis.
Use the node ID and ingest key from the workspace. For Reelay Cloud, use https://api.usereelay.com as the SDK endpoint. For Enterprise Agent, use the customer-owned HTTPS ingest endpoint supplied by your administrator.
3. Install the matching SDK
Initialize once when the application starts. For a browser app, initialize before rendering. For a backend, add the request middleware around your routes so errors include HTTP context.
4. Send a test error
Trigger a controlled test error in staging using your SDK guide. Avoid a test route that can be called in production.
Open Errors and find the occurrence. Check its node, environment, request details, and stack trace.
For browser-to-backend linking, make a request from the instrumented browser to the instrumented server. Check that both sides share the trace and session context.
Remove the test trigger when you finish.
5. Add source context and response ownership
Connect GitHub in Integrations and grant access to the relevant repositories. Stamp each deployment with its release and full Git commit SHA so analysis can inspect the correct revision. Assign service owners and connect the notification channels your team uses.
Starting with code scanning?
You can connect GitHub and run a branch scan without installing an SDK. Choose a repository and ref in Code Analysis, then review each check and finding. Add production error tracking when you need runtime evidence.