Skip to main content
Squasher log connectors let you route platform logs, drains, and pipeline output into the same project that powers your SDK-based errors. Before you add volume, read Design Queryable Logs. It explains canonical operation events, typed attributes, trace correlation, privacy, and outcome-aware sampling. Use connectors when you want fast coverage for infrastructure, worker, proxy, or platform logs. Keep the SDK for rich stack frames, user context, and release metadata.

​
Choose the right path

​
Setup flow

1

Create a connector

In Squasher, create a connector for your project and choose the source type you want to receive.
2

Copy the destination details

Each connector exposes a destination URL, required headers, and a status value. Keep those values in your log source, agent, or pipeline config.
3

Send a test log

Emit a single error-level event first. Once verification passes, widen the source to production traffic.

​
Verify

  • Confirm the connector shows a recent delivery time.
  • Check that an error-level event creates an issue in Squasher.
  • Check that surrounding info and warning logs show up as timeline context.

​
Migrate

For migrations, run the old destination and Squasher in parallel for a short window, compare event volume and fields, then switch alerts and dashboards once the new path is stable. Migration guides:

​
Hot-swap checklist

  • Start with one project or service instead of the whole account.
  • Keep field names stable for service, environment, level, and request identifiers.
  • Lower noisy filters before cutover so alert volume stays predictable.
  • Rotate the connector key after migration if the destination was shared during testing.

​
Manage connectors with the API

The control plane for connectors is available in the Log Connectors API reference. Use it to list the connector catalog, create connectors, verify delivery, update settings, and rotate keys.

​
Agent handoff

Use squasher log-connectors ..., the Log Connectors API, or MCP search("logConnectors") followed by execute.