Skip to main content
Vector is a good fit when you already collect logs from files, containers, or upstream services and want one place to normalize them before they reach Squasher.

​
Setup

1

Create a Vector connector in Squasher

Create the connector for your project, then copy the destination URL and headers from the connector details.
2

Add an HTTP sink in Vector

Point the sink at the Squasher destination and send newline-delimited JSON:
3

Normalize a few core fields

Preserve message, level, timestamp, service, and environment if you already have them. If not, use a Vector transform to map them before delivery.

​
Verify

  • Run vector validate against the config.
  • Send a single test event with level = "error".
  • Confirm the connector status in Squasher changes to healthy and the event lands in the correct project.

​
Migrate

If Vector currently fans out to another log product, add Squasher as a second sink first. Compare field coverage and alert behavior before removing the old destination.

​
Hot-swap

  • Keep batching enabled to reduce overhead.
  • Add a dedicated route or transform for noisy debug logs if you do not want to forward everything.
  • Rotate the connector key after cutover if the config was shared across environments.

​
Agent handoff