One control room for everything that moves
See which runs are healthy, which assets are stale and which sources are failing, without searching through logs on five machines. When something breaks, you get an alert with the context to fix it.
Run timeline: listings_sync (run_b19c)
Built for the person on call
Runs and logs
Every run has a timeline, step logs written with ctx.log, retry history and the exact inputs. Filter by pipeline, source, status or time.
Asset health
Each asset shows freshness, last successful run, check results and row counts, so you see problems before your users do.
Alerts
Send alerts to Slack, PagerDuty or email. Rules can match a pipeline, a source, a check or a cost threshold.
Stop the damage first, investigate second
If a provider is down, hammering it with retries helps nobody. Synchronoid pauses a source that keeps failing and alerts you. You can also pause or resume a source yourself from the control room or from the CLI.
- Routing by severity: warnings to Slack, outages to PagerDuty.
- Alerts include the failed step, the error and a link to the run.
- Resuming a source continues from where it stopped, with no duplicates.
$ syn runs list --status failed --since 24h run_b19c listings_sync failed Retry limit reached $ syn sources pause partner_listings_eu Paused partner_listings_eu. 3 queued runs on hold. $ syn sources resume partner_listings_eu Resumed. Queued runs will start within the rate budget.
Bring your own tools
Export traces and metrics with OpenTelemetry to the monitoring system you already use. The control room stays the best place to understand data, and your existing dashboards stay useful for infrastructure.
Ready to stop babysitting pipelines?
Synchronoid is in private beta. Tell us about your data and we will get you a workspace.