On-call roster
Who owns overnight pipeline breaks — without adding a second paging product.
On the roadmap
This solution is planned — not live yet. Related VectorData capabilities that already ship are linked below.
Use case · Roadmap
Pipeline on-call
Escalation and mute windows for data incidents — without pager chaos.
The problem
When dbt fails at 2am, everyone is “on call” or nobody is. Mute windows live in someone’s head. Escalation is a DM, not a roster.
The outcome
Planned: on-call roster, mute windows, and calm routing so one root-cause alert reaches the right person — built on today’s Watchdog queue.
Soon
Roster & mute windows planned
1 alert
Per root cause (already live)
Slack-ready
Routing destinations on roadmap
Capabilities
Mute windows
Quiet hours and maintenance so expected downtime does not page the team.
Calm escalation
If the first owner does not ack, escalate once — not a storm of duplicate pings.
Foundation already shipping
Watchdog + freshness + dbt triage exist today; roster UX is the missing layer.
- ✓Incident queue and grouping are live in the VectorData command center
- ✓Alert destinations and mute windows are on the product roadmap
- ✓Metadata-only — no need for a second agent in your VPC
- ✓Start with Watchdog today; add on-call when the roster ships
Related
Watchdog / Fix first
AI ranks stale tables, failed dbt runs, and cost spikes into one Fix-first queue.
Read →Executive KPI trust
Know the KPI tables are fresh before the Monday leadership meeting.
Read →Board deck confidence
Freeze the numbers that go in the board pack — with a freshness check first.
Read →Data contracts / SLOs
Freshness targets and owner expectations per table — on the roadmap.
Read →