> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sazabi.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Render

> Add a workspace-wide Render log stream pointed at Sazabi to forward service logs without connecting a Render API key.

[All Render integration capabilities](https://docs.sazabi.com/catalogs/integrations/render)

## About

Send your Render service logs — from web services, background workers, cron jobs, and databases — to Sazabi by configuring a workspace-wide log stream in the Render dashboard.

Render also has a **Connect your account** path where Sazabi sets up a per-service log stream for each service you pick. See [Render account connection page](https://docs.sazabi.com/catalogs/log-sources/connect-your-account/render.md) for that setup.

> [!WARNING]
>
> This log stream is **workspace-wide** — Render sends logs from every service in the workspace. To forward logs from individual services only, connect your Render account and Sazabi sets up a per-service log stream for each one.

## Prerequisites

* A Render workspace.
* Your Sazabi intake URL and stream token (both shown in the log stream setup panel above).

## Set up in the dashboard

**Step 1**

### Open Log Streams

In your [Render dashboard](https://dashboard.render.com), open the workspace you want to forward, then go to **Workspace Settings > Log Streams** and add a log stream.

**Step 2**

### Set endpoint and token

Paste the endpoint and token (shown above in the log stream setup panel) into the log stream form.

**Step 3**

### Save

Save the log stream. Render begins forwarding logs immediately.

## Set up with the CLI

You can also register the Render log source with the [Sazabi CLI](https://docs.sazabi.com/reference/cli.md) (installed and authenticated — see [CLI reference](https://docs.sazabi.com/reference/cli/log-sources.md)).

Registering the source mints the same intake URL the dashboard shows above (the public key is embedded in its hostname):

```bash theme={"system"}
sazabi log-sources create render --mode manual
```

The command prints the intake URL for the new source — copy the whole URL and point your sender at it using the configuration shown above. Run `sazabi log-sources get <log-source-id>` at any time to reprint the endpoint, or `sazabi log-sources list` to see every log source in the project.

## Verify

Trigger activity in your Render workspace — deploy a service or hit an application route. Open the [Intake page](https://docs.sazabi.com/guides/instrument/intake.md) in the Sazabi dashboard and confirm logs from the **Render** source appear. Logs typically appear within a few minutes of the activity.

## Troubleshooting

**No logs after saving** — Confirm you used the endpoint and token shown in the Sazabi log stream setup panel, not a generic HTTPS URL. Render's log stream uses a separate stream token for authentication, not the public key embedded in the intake hostname.

**Logs from services you did not expect** — This path is workspace-wide. Render sends logs from every service in the workspace. To scope to specific services, connect your Render account instead.

## Further reading

> [card] [Intake](https://docs.sazabi.com/guides/instrument/intake.md)
>
> See per-source ingestion volume and health in the Intake page.

> [card] [Render (connect your account)](https://docs.sazabi.com/catalogs/log-sources/connect-your-account/render.md)
>
> Let Sazabi set up per-service log streams for the Render services you pick.

> [card] [Log sources](https://docs.sazabi.com/catalogs/log-sources.md)
>
> Browse the full log source catalog.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.