Monitoring
Know when data is late, short or different.
Most failures that reach a dashboard are jobs that succeeded on the wrong data. Tidewater checks the data itself: when it arrived, how much of it there is, and whether its shape changed.
Freshness
Write the deadline the way you would say it.
Type "updated by 06:00 on weekdays, in New York time" and Tidewater turns it into a check. Holidays, daylight saving and time zones are handled for you, and every rule has an owner.
- One sentence per table, readable by anyone on the team
- Time zone aware, so a deadline stays correct across daylight saving changes
- Rules live in the product and in the API, so you can review them in code
orders_daily should be updated by 06:00 on weekdays in America/New_York. Alert finance-data when it is 15 min late.
| Table | Rule | Owner |
|---|---|---|
| orders_daily | Updated by 06:00 on weekdays | finance-data |
| payments_ingest | Updated every hour, within 15 minutes | payments-data |
| inventory_snapshot | Updated every 6 hours | supply-data |
Learned thresholds
Tidewater learns what normal looks like.
From two weeks of history Tidewater learns when each table usually lands and how that varies by weekday. You choose the deadline that matters to your readers. Tidewater tells you when a table drifts toward it.
- Weekday and month-end patterns learned automatically
- Fixed thresholds from day one, learned ones after two weeks
- Change a threshold by hand and the change is recorded with your name
Volume
A table can be on time and still be wrong.
A feed that arrives at 05:10 with 40 percent of its usual rows is worse than one that is late, because nobody notices. Volume checks compare each load with the range Tidewater expects for that day.
- Row counts compared with the learned range for the weekday
- Weekend and holiday dips are learned, not flagged
- Custom SQL checks on Team and Business plans
Schema
See the column that changed before a model breaks.
When a source adds, removes or retypes a column, Tidewater shows the diff and the models that read it, so the person who owns the change hears about it before the nightly build fails.
- Added, removed and retyped columns, with the time of the change
- Readers of each changed column listed through lineage
- Routed to the owner of the source, not to everyone
Under the hood
How it works, briefly.
Metadata only
Tidewater reads table names, column types, row counts and update times. It does not read table contents unless you write a custom SQL check.
Checks as often as you need
Every 15 minutes on Free, 5 on Team and 1 on Business. Where an orchestrator sends events, Tidewater reacts to the event instead of waiting for the next check.
Light on your warehouse
Freshness and volume come from system tables and run events, so a check costs a metadata query rather than a table scan.
Related documentation
See your own pipelines in Tidewater
Book a 30 minute walkthrough. We connect a sample of your setup and show you what it would have caught last month.