Data monitoring and support

Data monitoring and support keeps the data your business reports on arriving on time and correct. Every critical feed is checked each day, and a late or failed load raises an alert that names the feed. We read the vendor changes that would break a pipeline and act on them before their date.

Last reviewed

Feed freshness log, example

3 late or failed loads in 30 days, all caught before the 9am report

Example data
FeedExpected byEach day, 1 to 30 SeptemberOn timeLate or failed
Orders06:0030 days checked300
Stock06:0030 days checked291
Ad spend06:3030 days checked291
Web analytics07:0030 days checked300
Ledger07:3030 days checked291

150 checks, 147 on time, 3 late or failed

5 feeds checked on 30 days is 150 checks, and 147 on time leaves 3 late or failed
The three exceptions
DateFeedExpected byCaughtStatusCaught before the 09:00 read by
Wed 9 Sep 2026Stock06:0006:15Late2h 45m
Mon 14 Sep 2026Ad spend06:3006:45Failed2h 15m
Thu 24 Sep 2026Ledger07:3007:45Late1h 15m
The narrowest margin was the ledger on 24 September, caught at 07:45, 1h 15m before the 09:00 read
Example data: an invented September 2026, with five feeds checked every day from 1 to 30 September. Two loads arrived late and one failed, and the check caught each of them at least 1h 15m before the dashboard was read at 09:00.
Show the numbers
The month by feed, example data
FeedExpected byDays checkedOn timeLate or failed
Orders06:0030300
Stock06:0030291
Ad spend06:3030291
Web analytics07:0030300
Ledger07:3030291

What data monitoring fixes

The dashboard is blankMonday's figures are missing, and nobody can say whether the data is late or gone.
Old numbers that look currentA feed stopped loading, and the report went on showing the last figures it had until someone noticed they never moved.
An account nobody can openThe platform runs on a login and an inbox that belonged to someone who has since left.
Reports that stood stillThe dashboards were built once, and the business has changed around them since.

What the support includes

Daily freshness checksEach critical feed is checked every day for arrival and freshness, and a late or failed load raises an alert that names the feed.
Vendor watchWe read platform changes, deprecations and retirements that would break a pipeline, and act on each before its date.
A committed responseWhen a dashboard goes down, we respond within business hours and inside the response time written into your agreement.
The monthly health noteEach month you get a note on how the platform and its feeds ran.
Improvement hoursEvery level includes hours for new measures, new reports and fixes, so your reporting keeps moving forward.

Your reporting runs on data that arrives every morning. We check that it did, and you hear from us before your board does.

How support runs

  1. 1

    Starting point

    Support begins from a platform we built, or from one we take over after a short review.

  2. 2

    Every day

    The checks run on each critical feed, and any late or failed load raises an alert.

  3. 3

    Every month and quarter

    The health note arrives monthly. From the second level up, a quarterly review sets a roadmap, and the improvement hours work through it.

  4. 4

    You own it

    The platform sits in your cloud account, on your billing, with admin access for us. Nothing sits in an account that belongs to one person.

Where data pipelines fail

A data platform vendor retired an old version of its product, and the notices went to one person's inbox. Nobody acted, the workspace was deleted, and months later a dashboard a client relied on was blank, with the data sent in the meantime lost. Nobody was at fault, because nobody owned the platform.

A feed that stops quietlyA report reading a dead feed keeps showing its last figures, so the daily check on each critical feed raises an alert the morning the feed fails to arrive.
A fault outside the platformSupport does not cover outages at the cloud or BI vendor, or changes to source systems and ingestion code that your own developers control. When one of those breaks your reporting, we tell you what broke and who has to fix it.

In the example, the check caught the late ledger at 07:45 on 24 September, an hour and a quarter before the dashboard was read.

Managed data services at three levels

Keeping it runningThis level covers the daily checks, the vendor watch, the committed response, the monthly health note and a set of improvement hours.
Running and improvingEverything in the first level comes with a quarterly review and roadmap, and with more improvement hours.
EmbeddedEverything in the second level comes with more improvement hours again, and with new dashboards and reporting built for further teams or for your customers.

Where monitoring fits

Monitoring sits on the platform that data strategy and infrastructure work puts in place, and it keeps the dashboards and BI on top of it fed. A business reporting in Power BI gets the same checks on the feeds behind its models, alongside the build work of a Power BI consultant. When the business needs someone to run the whole analytics function, monitoring becomes part of fractional analytics.

Questions about data monitoring

Is this data observability?

Yes, for the feeds your reporting depends on. Data observability means knowing when data in use is late, missing or wrong. Here that means a daily freshness check on each critical feed, an alert when a check fails, and a monthly health note on how the platform ran.

Do you offer Power BI support?

Yes. Power BI support covers the reports and the feeds behind them, with a daily check that each feed arrived, a committed response when a report goes down, and improvement hours for new measures and report pages.

How quickly do you respond when a dashboard goes down?

Within the time written into your agreement. Each business agrees its own response times with us, and those times go into the agreement in writing. Every response happens within business hours.

What does support not cover?

Outages at the cloud or BI vendor, and changes to source systems or ingestion code that your own developers control. When one of those breaks your reporting, we tell you what broke and who has to fix it.

Can you support a platform you didn't build?

Yes. Support starts from a platform we built, or from one we take over after a short review. Either way, the platform sits in your cloud account, on your billing, with admin access for us.

Would you know today if a feed behind your reports had stopped?

On the call we list the feeds behind your morning reports and say which ones a daily check should cover first.

Book a call

Free 30 min call