Skip to main content

​
Overview

Render uses an API key rather than third-party OAuth for this setup. Paste the key once and select a workspace. Squasher shows the services that the workspace connection covers.

​
One-click setup

  1. Create a Render API key with access to the target workspace.
  2. In Squasher, open Integrations > Render, paste the key, and select the workspace.
  3. Review the current workspace log and metric destinations.
  4. Confirm setup and run the opt-in test.
Squasher uses the workspace stream APIs when the Render plan and destination type support them. A custom Render log destination uses TLS syslog, not a general HTTPS request. Squasher uses bounded API pulling when a compatible stream is unavailable. Custom OpenTelemetry metric streams require a supported paid Render plan. See Render’s log stream and metric stream plan and protocol details. Each workspace has a default log stream and metric stream. Squasher does not replace a destination owned by another tool. It reports the conflict and uses the safe pull fallback when possible.

​
Manual setup

1

Get your drain URL

If Squasher shows a managed TLS syslog destination, copy its host, port, and token. If no TLS destination is available, keep the API pull mode selected.
2

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 destination to the TLS syslog address from Squasher
  5. Save the stream
3

Verify

Trigger an error in your Render service. It appears in your Squasher dashboard within seconds.

​
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