Render
Connect your Render account so Sazabi can configure a per-service log stream for each service you select.
About
Render log streams forward logs from your web services, background workers, cron jobs, and databases to Sazabi over a regional syslog endpoint. Connecting your Render account lets Sazabi set up a per-service log stream for each service you pick.
Render also has a Send to an endpoint path where you configure a workspace-wide log stream yourself in the Render dashboard. See Render endpoint page for that setup.
Per-service log stream selection requires a Render workspace on the Scale or Enterprise tier. The workspace-wide log stream (available on other tiers) can be configured using the send-to-an-endpoint path.
Prerequisites
- A Render workspace (Scale or Enterprise for per-service selection).
- A Render API key created in your Render dashboard.
Set up in the dashboard
Create a Render API key
Create an API key in your Render dashboard (Account Settings > API Keys). The key starts with rnd_.
Connect in Sazabi
Go to Settings > Log streams, click Add source, and select Render. Enter your Render API key. Sazabi fetches your workspaces — select the one you want to connect and click Connect.
Add log streams
After the connection is confirmed, click Add log stream to open the service picker. Sazabi lists all services in the connected workspace. Select the services you want to forward — web services, background workers, cron jobs, and databases are all supported.
Set up with the CLI
You can also connect the Render log source with the Sazabi CLI (installed and authenticated — see CLI reference).
Create a managed connection by passing your API key and the Render workspace (owner) ID as metadata:
sazabi log-sources create render --mode managed \
--metadata '{"apiToken":"'"$RENDER_API_KEY"'","ownerId":"<your Render workspace ID>"}'The ownerId is the Render workspace this key belongs to (the dashboard flow discovers it for you from a workspace picker). Sazabi validates the key against the Render API and creates the log source; note the log source ID it prints.
Add a log stream — one per Render service — with sazabi log-streams create, passing the Render service ID and name in --config:
sazabi log-streams create --log-source-id <log-source-id> \
--config '{"serviceId":"<your Render service ID>","serviceName":"<service name>"}'Run sazabi log-sources list to confirm the source and its streams.
Verify
Deploy a new version of a connected service or send traffic to one of its routes.
Open the Intake page in the Sazabi dashboard and confirm that records attributed to the Render source appear. Logs typically arrive within one to two minutes of the service starting to deliver them.
Troubleshooting
Token validation fails — Confirm the API key starts with rnd_ and was generated in your Render dashboard.
Per-service selection not available — Per-service log stream overrides require the Scale or Enterprise plan. On other plans, use the workspace-wide log stream path instead.
Logs stop arriving — The log stream may have been removed or the API key revoked. Remove and re-add the log stream from Settings > Log streams in Sazabi to reprovision it.