DATA OPS

Snowflake table freshness SLA monitor with Slack alerting

Checks the last-loaded timestamp of every SLA-tracked Snowflake table on a schedule and posts a Slack alert listing only the tables that have gone stale past their freshness…

CategoryData Ops
Enginesim
Difficultybeginner
Triggerschedule
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerEvery 15 minutes (schedule)
  • ActionQuery MAX(loaded_at) per tracked tableSnowflakeSnowflake
  • LogicCompute staleness vs each table's SLA
  • LogicStop if no tables breached
  • OutputPost breached tables to #data-oncallSlack

What it does

Queries Snowflake for the most recent load time of each table you track, compares it against that table's freshness SLA, and alerts your data team in Slack the moment a table falls behind. No more discovering stale dashboards from a confused stakeholder.

When to use it

Run it when you maintain a set of business-critical tables (revenue, sessions, orders) with explicit freshness expectations and want a single, deduplicated alert instead of per-table noise. Ideal for hourly or every-15-minute cadences.

How it works

  1. 1A schedule fires the run (e.g. every 15 minutes).
  2. 2A Snowflake query reads `MAX(loaded_at)` per tracked table from your metadata or `INFORMATION_SCHEMA`.
  3. 3A logic step computes age = now - loaded_at for each table and keeps only those exceeding their configured SLA in minutes.
  4. 4A second logic step short-circuits the run if the breach list is empty, so healthy cycles stay silent.
  5. 5A Slack message posts the breached tables, their staleness, and owning team to the data on-call channel.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect SnowflakeWarehouses, queries, shares.
  2. 2
    Connect SlackChannels, DMs, threads, mentions.
  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.