DATA OPS
Reverse-ETL sync-lag SLA monitor with escalation
On a schedule, measures the lag between the latest BigQuery load timestamp and the latest synced timestamp in Salesforce, emits the gap as a Datadog metric.
How it runs
The automated pipeline, trigger to output.
- TriggerSchedule every 15 minutes
- ActionRead latest source load timestamp from BigQueryBigQuery
- ActionRead latest synced timestamp from SalesforceSalesforce
- ActionEmit freshness lag as a Datadog gauge metricDatadog
- LogicBranch when lag exceeds the SLA threshold
- OutputOpen a PagerDuty incident with lag detailsPagerDuty
What it does
Most reverse-ETL tooling reports "sync succeeded" even when the data it pushed is hours behind the warehouse. This workflow measures actual data freshness: it reads the maximum updated-at timestamp from the BigQuery source table and the maximum synced timestamp landed in Salesforce, computes the lag, and ships it as a Datadog gauge so you get history, dashboards, and anomaly detection. When the lag crosses your SLA, it opens a PagerDuty incident so on-call can intervene before reps act on stale records.
When to use it
Use it when sync freshness is operationally critical and you already run on-call rotations. It treats data lag like any other production SLO rather than something you discover from an angry sales manager.
How it works
- 1A frequent schedule (e.g. every 15 minutes) triggers the check.
- 2Read the latest source load timestamp from BigQuery.
- 3Read the latest synced timestamp from Salesforce.
- 4Compute the freshness lag and emit it as a Datadog metric.
- 5Branch: if lag exceeds the SLA threshold, escalate.
- 6Open a PagerDuty incident with the measured lag and affected object.
Set it up
What you configure once, before turning it on.
- 1Connect BigQueryDatasets, queries, schemas.
- 2Connect SalesforceAccounts, opportunities, cases.
- 3Connect DatadogMetrics, traces, log search.
- 4Connect PagerDutyIncidents, on-call, escalations.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Data Ops workflows
Weekly BigQuery Cost Trend Sheet and Exec Digest
Compiles week-over-week BigQuery scheduled-query cost by owner and dataset into a Google Sheet with trend columns.
Daily BigQuery Scheduled-Query Cost Attribution to Owners
Each morning, totals the prior day's on-demand bytes-billed per scheduled query, maps each query to its owner from a label, and posts a per-owner cost leaderboard to Slack.
BigQuery Per-Team Budget Breach Alert to PagerDuty
Tracks month-to-date BigQuery scheduled-query spend per team and, when a team crosses its monthly budget, pages the team's on-call in PagerDuty and snapshots the spend breakdown…
dbt source freshness watcher with severity-routed alerts
Checks Snowflake loaded-at timestamps against each dbt source's freshness SLA, then routes warnings to Slack and hard breaches to a PagerDuty incident so stale data never…
dbt orphan model detector with Linear cleanup tickets
Scans your dbt manifest for models that no other model, exposure, or BI tool consumes.
Raw Sensor Telemetry Archive to BigQuery
Captures every incoming building sensor reading via webhook, normalizes the payload into a consistent schema.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.