← Back to parent Epic
MAZENG-FT-46 · Trustworthy service health and history
Why it matters
Users need to distinguish a Maze service incident from a problem limited to their own project.
Expected outcome
Users can make informed decisions from current, timestamped service health and accurate incident history.
In scope
- Current status for every governed Maze service.
- Accessible service history with explicit timestamps and incident semantics.
- Explicit loading, empty, stale, and failure states.
- Delivery status
IN_BACKLOG- Owner
- RootAtSkic (product lead)
- Solution approval
- PENDING
Acceptance
Acceptance outcomes
- 01
Public status shows a current state and timestamp for every governed service.
- 02
Users can inspect an accurate 30-day history with accessible incident semantics and honest regional availability.
- 03
Empty, stale, loading, and API-failure states are explicit.
Dependencies and risks
Dependencies
None recorded.
Risks
- Reliable probes, retention, service inventory, timezone rules, and incident semantics are not yet defined.
- Legacy retention covers about ten days despite presenting a 30-day history.
- Legacy sorting and regional-status logic can present incorrect output and must not be preserved.
Authoritative Architecture tasks
No authoritative Architecture tasks are linked.