Freshness Monitor
Currency is data, not a vibe. The pipeline computes a per-sport coverage_status in the ops.freshness view; this panel reads it straight through. The interesting cases are the two that are not a simple green/red — read them carefully below.
Monitored
4
curated verticals
Current
3
level with vendor
Behind
0
vendor ahead of us
Vendor unknown
1
cursor unreadable
3/4 current, 1 vendor_unknown — no sport is behind. The one non-green sport is a monitoring gap, not a stale feed.
lag_days negative: a loaded event is dated ahead of the vendor's last completed event.
Two orders of magnitude larger than the others — always LIMIT exploratory queries here.
competitors = 47 TEAMS, not people. Real people live in masl_players.
vendor cursor could not be read (NO_KEPT_SESSIONS=1). A MONITORING gap, not stale data.
vendor_unknown is a monitoring gap — not stale data
HLR reports coverage_status = vendor_unknown (gap F8). The pipeline could not read the vendor's cursor (NO_KEPT_SESSIONS=1), so is_current and lag_days are NULL.
The HLR data we hold is loaded and queryable — its last_run_status is OK. What is unknown is whether the vendor has newer events we haven't seen. Never render vendor_unknown as behind.
A negative lag is ahead, not behind
SMX shows lag_days = -3. That is nota stale feed — a loaded event is dated ahead of the vendor's last completed event (e.g. a scheduled round we already have on the calendar).
It stays current. Treat only a positive lag as evidence the vendor is ahead of our load.
The monitoring schema — ops.freshness
A Redshift view. Per-sport currency. These are the real columns a prospect gets to query — the currency answer is a first-class, auditable object, not a status page scraped after the fact.
Live-shaped output — the `freshness` canned query
SELECT sport, coverage_status, is_current, lag_days,
latest_event_loaded_utc, last_run_status, last_run_utc, note
FROM ops.freshness
ORDER BY sport;| sport | coverage_status | is_current | lag_days | latest_event_loaded_utc | last_run_status | last_run_utc |
|---|---|---|---|---|---|---|
| hlr | vendor_unknown | NULL | NULL | 2026-07-26 03:12:00 | OK | 2026-08-10 06:00:11 |
| masl | current | true | 0 | 2026-07-29 04:45:00 | OK | 2026-08-10 06:01:03 |
| smx | current | true | -3 | 2026-08-02 02:20:00 | OK | 2026-08-10 06:00:44 |
| wsl | current | true | 0 | 2026-08-08 21:05:00 | OK | 2026-08-10 06:02:29 |
Label: Real coverage_status per sport; timestamps illustrative. vendor_unknown is a monitoring gap, not stale data.
Timestamps are illustrative; every coverage_status is the real 2026-08-10 value. Pulled with AWS_PROFILE=asd against Redshift Serverless (us-west-1 / default-workgroup / dev).