Skip to main content
Squasher reads the logs and metrics of a Render workspace through the Render API. Render log streams use syslog, which Squasher does not accept, so Squasher pulls the logs every 5 minutes instead.

​
Prerequisites

  • A Render API key that can read the workspace. Create it in your Render account settings.
  • A Squasher API key with the project:write permission, saved as SQUASHER_ADMIN_KEY. See Provider connections.
  • The Squasher project ID, saved as SQUASHER_PROJECT_ID.

​
Connect the workspace

1

Find the workspace ID

The response lists each workspace with its id and name.
2

Connect it

Squasher stores the Render key encrypted and creates its own ingest key for the connection. The response lists the services it found, and streams shows how logs and metrics arrive: poll or push.
Squasher also asks Render to stream workspace metrics to Squasher. If the workspace already streams metrics to another destination, Squasher keeps that stream and pulls metrics instead.

​
What Squasher keeps from each record

Metrics arrive as gauges named render.<metric>, with the Render labels as attributes.

​
Verify

  1. Write one line at error level from a Render service.
  2. Wait up to 5 minutes for the next pull.
  3. In Squasher, select Issues in the sidebar. The error is at the top of the list.
To check the connection, send GET .../provider-connections/render. It shows the status, the last_error, and the resources that Squasher owns.

​
Limits

  • Logs arrive in batches every 5 minutes, not in real time.
  • Logs from preview instances arrive only when include_preview_logs is true.
  • Log lines have no environment, so automatic AI triage does not run on their issues.
  • If Render rejects the API key, the connection changes to reconnect_required.
  • To disconnect, send DELETE .../provider-connections/render.
For stack traces, also add the Node.js SDK or OpenTelemetry to the service.

​
Next steps

Provider connections

See how connections work and how to remove them.

OpenTelemetry

Send traces and error spans from the service.