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

# Render

> Receive errors from Render services via log streams. Zero-code setup.

## Overview

Render supports HTTP log streams that forward your service logs to external destinations. Point them at Squasher to capture errors from all your Render services.

If you use the Log Connectors screen in Squasher, create the Render connector first and copy the managed endpoint and ingest key from there. The manual URL below uses the same drain destination shape.

## Setup

<Steps>
  <Step title="Get your drain URL">
    Your Squasher drain URL:

    ```
    https://ingest.squasher.ai/v1/drain/render/YOUR_PROJECT_ID
    ```
  </Step>

  <Step title="Add the log stream in Render">
    1. Go to your Render dashboard
    2. Navigate to **Account Settings > Log Streams**
    3. Click **Add Log Stream**
    4. Set the endpoint to your drain URL
    5. Add a custom header: `x-squasher-key: sq_pk_your_api_key`
    6. Click **Save**
  </Step>

  <Step title="Verify">
    Trigger an error in your Render service. It appears in your Squasher dashboard within seconds.
  </Step>
</Steps>

## What Gets Captured

Squasher ingests all Render log entries and detects errors via:

* Severity field: `error`, `fatal`, `critical`
* Message heuristics: lines containing `Error`, `Exception`, `panic`, `fatal`
* HTTP status codes >= 500 (for web services)

## Combining with SDK

For richer error context, also install a Squasher SDK or configure OpenTelemetry in your Render service. The log stream catches infrastructure-level errors while the SDK provides stack traces and user context.

## Agent handoff

```text theme={null}
Set up Render log forwarding into Squasher for project <project_id>. Prefer a managed log connector, keep the first service narrow, verify with one error, and add an SDK later when stack traces or user context are needed.
```