Observability
Know what moved. Know what failed. Know why.
Every run is recorded stage by stage. Failures name the field and the reason, in plain language, with a suggested fix.
01 — Monitoring
Six views, one run history.
Switch between health, runs, errors, latency, logs and alerts. In the Errors view, try Fix, Retry and Ignore.
OBSERVABILITYLast 30 daysSample workspace
Operations0.00Msample, 30 days
Success rate0.00%Healthy
Average latency0msp95 2.1s
Failed runs23
Operations per dayred ticks: days with failed runs
30d ago15dtoday
| Flow | Health | Operations | Success | Avg latency | Last run |
|---|---|---|---|---|---|
| shopify_orders → erp_sales_orders | healthy | 612,430 | 99.75% | 780ms | 2m ago |
| crm_contacts → warehouse_dim_customer | healthy | 418,200 | 99.72% | 910ms | 14m ago |
| product_events → billing_items | healthy | 301,150 | 99.71% | 820ms | 1m ago |
| partner_a → partner_b_orders | healthy | 240,800 | 99.73% | 870ms | 6m ago |
| legacy_files → orders_api | healthy | 150,300 | 99.65% | 880ms | 3h ago |
| inventory_sync (two-way) | healthy | 97,120 | 99.67% | 840ms | 9m ago |
| All flows | 1,820,000 | 99.72% | 840ms |
Flows below 99.65% success are marked degraded. Sample data for the last 30 days.
Sample data · demo values, not measurements
02 — What you can see
From a spike to a single field.
Health
Which flows are healthy, which are degraded, and why.
Run history
Every run with its trigger, records, duration and per-stage timing.
Field-level errors
The exact field, the value pattern and what the destination expected.
Alerts
Notify your team on failure rate, latency or a silent flow.
Stop building the same integration twice.
Connect your systems once.Translate your data reliably.Keep every workflow moving.