diditarrive
Sign inSign up

Use case

The feed the warehouse loads from, watched at the door.

An upstream system writes a daily extract into a container in Azure Blob Storage, and the warehouse load runs against whatever is there at 04:00.

How it fails today

The load succeeds on stale files, because a loader reading a folder cannot tell the difference between today’s extract and yesterday’s. The failure surfaces as numbers that look plausible and are a day old.

month endThe discrepancy is found against a period nobody can re-run.

What we do about it

A night, as we would run it
  1. from 01:00We list the container prefix through the window.
  2. 03:30Due passes with nothing new in the window.
  3. 04:00Grace ends, before the load runs. One alert.
  4. 04:26The extract lands. One closing alert, with its size.

What we need

An account, a container and a SAS token scoped to the one prefix we list. The full posture.

one containerlistings, not contentswritten once
The monitor, configured

Nightly warehouse extract

Where
Azure Blob, exports/daily
When
daily by 03:30
Grace
30 minutes
Why that grace
the load starts at 04:00

If the key expires, that’s Check broken, never Missed - broken access is its own alert, and it says whose job it is to fix.

Set it up in a sentence:

“The warehouse extract lands in Azure Blob under exports/daily by 3:30am, give it 30 minutes.”

Create monitor
Same shape, different plumbing:The connectorsThe schedule modelPricing
Menu
ProductUse CasesConnectorsPricingTrustSign inSign up