Nodes & releases
Give each runtime a stable identity and connect events to the deployed code.
What is a node?
A node represents an instrumented application or service, such as a browser frontend, checkout API, or background worker. It connects incoming telemetry to the right environment and repository.
Create and configure a node
Open Nodes and create a node with a name your team recognizes.
Choose its environment and repository where relevant.
Copy the node ID and ingest key into the SDK configuration. Use the HTTPS ingest endpoint for that node's deployment.
Keep the identity stable between releases. Create another node when the workload or operational boundary changes.
Identify the deployed revision
A release is the version of the artifact you shipped. A full commit SHA identifies its source revision. Backend SDKs can read these environment variables at initialization. In browser builds, supply release and commitSha from your build process.
REELAY_RELEASE=checkout@1.8.0REELAY_COMMIT_SHA=<full-git-commit-sha>Handle ingest credentials
Keep backend ingest keys in deployment secrets. A browser's configured ingest key is visible to anyone using the app, so treat it as a scoped telemetry credential. Never place GitHub, model-provider, or agent credentials in browser code. Rotate a node's credential when it is no longer appropriate to trust it.