Skip to main content
Squasher does not expose a dedicated Loki-compatible push endpoint yet. Use this path when you want to migrate a Loki-based pipeline into Squasher:
  1. Create the HTTP API connector in Squasher.
  2. Keep your current Loki flow running during a short dual-ship window.
  3. Re-map the outgoing payload at the collector or gateway layer so it posts structured JSON to Squasher’s HTTP API.
  4. Verify event volume, level mapping, and service tags before cutting over alerts.
If you need a temporary fallback, use HTTP API or Vector as the migration target.

​
Compatibility boundaries

  • No dedicated Loki push endpoint yet
  • Labels must be flattened or remapped before delivery
  • Query semantics stay in your existing pipeline, not in Squasher

​
Field mapping

  • Loki labels -> tags
  • Stream message -> message
  • Stream timestamp -> timestamp
  • Severity labels -> level

​
Troubleshooting

  • Drop high-cardinality labels before forwarding
  • Verify timestamps are RFC3339 or epoch values that your pipeline can translate cleanly
  • Start with a single translated stream before widening to all tenants

​
Agent handoff