DATA OPS

Freshness Lag Metric Emitter to Datadog

On a tight schedule, measures how many minutes behind SLA each critical Snowflake table is and pushes that lag as a custom metric to Datadog so you can chart trends and set your…

CategoryData Ops
Enginesim
Difficultyintermediate
Triggerschedule
Steps4
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerEvery 5 minutes schedule
  • ActionRead last-load timestampsSnowflakeSnowflake
  • LogicCompute per-table lag in minutes
  • OutputEmit lag as Datadog custom metricDatadogDatadog

What it does

Instead of deciding alert logic itself, this workflow turns warehouse freshness into observable metrics. Every few minutes it measures the lag, the gap between now and each table's last successful load, and emits that value as a per-table custom metric to Datadog. Your existing Datadog monitors, dashboards, and SLOs then own thresholds, alerting, and trend analysis, keeping freshness in the same observability stack as the rest of your infrastructure.

When to use it

Use this when your team already lives in Datadog and wants data freshness treated like any other signal, with historical graphs, anomaly monitors, and SLOs rather than one-off Slack pings.

How it works

  1. 1A frequent schedule, such as every five minutes, triggers the run.
  2. 2A Snowflake query returns the last-load timestamp for each monitored table.
  3. 3A logic step converts each timestamp into a minutes-behind-SLA lag value tagged by table.
  4. 4A Datadog action submits the per-table lag as a custom gauge metric for dashboards and monitors.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect SnowflakeWarehouses, queries, shares.
  2. 2
    Connect DatadogMetrics, traces, log search.
  3. 3
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  4. 4
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  5. 5
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.