DataOps & ETL monitoring
Dataventra Monitor
See every job, every run, every breach.
Monitor gives data teams one operational view of SQL Agent jobs, SSIS packages and pipelines — failures, SLA breaches, runtimes, record counts and data freshness, with the history to spot trends early.
Runs today
128
Failed
1Failed
SLA at risk
1SLA at risk
Last warehouse load
05:42
| Job / package | Status | Runtime | Rows |
|---|---|---|---|
| DW_Nightly_LoadSQL Agent | Succeeded | 42m 10s | 3,214,880 |
| SSIS_Stg_ERP_CustomerSSIS | Succeeded | 6m 48s | 184,220 |
| SSIS_Stg_CRM_AccountSSIS | Failed | 1m 12s | — |
| Fact_Sales_IncrementalSQL Agent | Running | 18m 03s | 1,106,432 |
| PBI_Refresh_SalesDataset | SLA at risk | — | — |
| DQ_Checks_FinanceSQL Agent | Succeeded | 2m 31s | 48 checks |
Runtime trend · DW_Nightly_Load (minutes)
Runtime anomaly · 58m run
The problem
An SSIS package fails at 2 a.m. The first alert is a business user at 9 a.m. asking why yesterday's numbers are missing.
Questions Monitor answers
- Which loads failed or ran late overnight — and what did they feed?
- Is the nightly warehouse load getting slower month over month?
- Did today's customer load bring in far fewer rows than usual?
- Which datasets are stale right now?
Capabilities
What Monitor does
- 01
Job & package execution
Track SQL Agent jobs, SSIS packages and pipeline runs with status, step-level detail and error output.
- 02
SLA & freshness tracking
Define when data must be ready and get flagged the moment a load is late, stale or at risk.
- 03
Runtime & volume trends
Compare runtimes and record counts against history to catch slow degradation and silent data loss.
- 04
Source-system activity
Understand when upstream systems deliver, so delays are traced to their origin instead of guessed at.
Other Dataventra solutions
See Monitor against your own environment.
We'll walk through how it maps to your systems, what setup involves and what you'd see in the first weeks.