Render

Forward logs from Render services to Sazabi for AI-powered analysis and investigation.

Render is a native data source, which means Sazabi provisions and manages the forwarding infrastructure automatically. Once you connect your Render account, logs from your selected services start flowing to Sazabi within minutes.

About this data source

Sazabi creates log streams for your Render services and configures webhook endpoints to receive log data. This allows you to centralize logs from your Render infrastructure for AI-powered analysis and investigation.

With Render log streams, you can:

Monitor web services, background workers, and cron jobs
Stream logs from static sites and private services
Investigate issues across your Render infrastructure
Correlate logs from multiple services in a single view

Prerequisites

Before you begin, make sure you have:

A Render account with active services
A Render API token (from your account settings)
Your Render Owner ID

Get your API token and Owner ID

Open account settings

Log in to your Render account and click on your profile in the top-right corner. Select Account Settings from the dropdown menu.

Create an API key

Navigate to the API Keys section and click Create API Key.

Name: Enter a descriptive name like "Sazabi Log Streaming"

Copy the API key immediately after creation. Render only shows the key once and you cannot retrieve it later.

Find your Owner ID

Your Owner ID is displayed in the Account Settings page. It is a unique identifier that starts with usr- for personal accounts or tea- for team accounts.

You can also find it in the URL when viewing your account settings: https://dashboard.render.com/u/{owner-id}

Connect Render to Sazabi

Open data sources

Data Sources

Add Render data source

Click Add Source and select Render from the list of available data sources.

Enter your credentials

Provide the following information:

API Token: Paste your Render API key
Owner ID: Enter your Owner ID (e.g., usr-abc123 or tea-xyz789)

Sazabi will validate your credentials and fetch your available services.

Select services to monitor

Choose which Render services you want to forward logs from. You can select:

Web Services
Private Services
Background Workers
Cron Jobs
Static Sites

Select individual services or monitor all services in your account.

Complete setup

Click Connect to finalize the configuration. Sazabi will automatically create log streams and webhook endpoints for your selected services.

What Sazabi creates

When you connect Render, Sazabi provisions:

Log stream per service: Each selected service gets its own log stream configuration
Webhook endpoint: A secure endpoint that receives log data from Render

These resources are managed automatically by Sazabi. You can view and modify which services are monitored from the Data Sources settings at any time.

Render log streams are created using the Render API. Sazabi manages the lifecycle of these streams, including creation, updates, and deletion when you disconnect the data source.

Verifying logs are flowing

Once you have connected Render, you can verify that logs are flowing to Sazabi:

Ask the assistant: Open a thread in Sazabi and ask "Show me Render logs from the last hour" or "What errors occurred in my Render services?"
Check the dashboard: Navigate to your project in the Sazabi dashboard to see logs appear in real-time.
Generate test logs: Trigger some activity in your services (e.g., make an HTTP request) to generate fresh logs.

Troubleshooting

Token permissions

If Sazabi cannot fetch your services, verify that your API token is valid and not expired. Render API tokens have full access to your account, so permission issues are typically caused by invalid or revoked tokens.

Owner ID mismatch

If you see an Owner ID error:

Verify the Owner ID matches your account type (usr- for personal, tea- for team)
Ensure you're using the Owner ID, not the service ID or environment ID
Check that the API token belongs to the same account as the Owner ID

Service not found

If a service is not appearing in the list:

Verify the service exists and is not suspended
Check that your API token has access to the service
For team accounts, ensure you have the correct permissions
Refresh the Data Sources page to fetch the latest service list

Logs not appearing

If logs are not flowing after setup:

Wait a few minutes for the log stream to initialize
Verify your services are running and producing logs
Check the Render dashboard for any service errors
Generate some traffic to your service to produce new logs

Webhook delivery failures

If Render reports webhook delivery failures:

The webhook endpoint may be temporarily unavailable
Render will retry failed deliveries automatically
Contact Sazabi support if failures persist for more than 30 minutes