System Health • CSync
Status
Operational visibility for the dashboard, API, and data pipelines. This page is ready to wire to backend status checks later.
All Systems Operational
Last updated: —
Foundation
What System Health should cover for CSync
Core app
Landing + login, dashboard load, auth session checks, and static pages uptime.
API & reporting
KPI endpoints, report exports, global date filter resolver, and latency/error rates.
Data pipelines
Ingestion freshness, marketplace feeds, retail media spend loads, and catalog health computations.
Planned maintenance
Scheduled downtime, backfills, schema changes, and known degradations during deploys.
Components
Service Status
These rows are intentionally named to match how you’ll wire backend checks later (API, pipelines, exports).
Web App
Landing, login, navigation, static pages
Operational
KPI API
Dashboard KPI endpoints, filter scoping
Operational
Reports & Exports
Report generation, CSV exports, endpoint consistency
Operational
Date Preset Resolver
Global date filter resolution (fiscal + rolling windows)
Operational
Data Freshness
Ingestion cadence, last successful load times
Operational
Wiring tip: map backend health checks to data-component-key and update the status pill + latency fields.
Support
Need help with an issue?
Include the preset + filters + export timestamp and we’ll triage faster.
Incidents
Incident History
Keep this lightweight at first: title, impact window, affected components, and resolution notes.
No incidents reported
When you wire backend reporting, this section can render recent incidents and link to details.
[Incident title]
[Short summary / customer impact]
Window: [start] → [end] • Affected: [components]
Maintenance
Planned Maintenance
No maintenance scheduled
When you schedule deploy windows or data backfills, list them here with expected impact (e.g., exports delayed, freshness lag).