Yatify Data Reliability Monitor
The operational layer behind Yatify: source checks, release freshness, validation state, schema-change detection and a publish gate that protects dashboards from silent source failures.
- Decision
- Know whether a dashboard is fresh and trustworthy before using its result.
- Source
- Yatify source-run logs + official source endpoints
- Period
- Continuous source checks
- Created by
- Nyashadzashe Munyati
The analytical result is shown before the technical method.
What I did in this project
Defined the question.
Prepared the data.
Built the analysis.
Validated and documented the result.
Know whether a dashboard is fresh and trustworthy before using its result.
A dashboard can look professional while being stale, incomplete or silently broken. The decision problem is whether today’s data products can be trusted.
Source data
Yatify source-run logs + official source endpoints
What I changed before calculating anything
Worked calculations — not black-box KPIs
What the drill-down adds
The headline chart gives the decision signal. These additional views show whether the same conclusion survives when the data is sliced another way.
The question and method are documented, but unfinished results are not presented as completed analysis.
What I would say in the management meeting
What I would do next
Shared hosting cron setup is provider-specific and must be scheduled after upload. Stats SA source formats can change, so the source monitor detects new releases while parsing remains validation-gated.