Story: Record service lifecycle events and surface them in system health
Table of Contents
This page documents a story in Sprint 30, carried unfinished from Sprint 28 at close. It captures the goal, current status, acceptance criteria, and the tasks that compose it.
1. Goal
Services announce their starts and graceful stops, telemetry records the events and raises restart notices, a service logs out on shutdown, and the system-health home shows the services.
2. Status
| Field | Value |
|---|---|
| State | BACKLOG |
| Parent sprint | Sprint 30 |
| Now | Not yet started. |
| Waiting on | Nothing. |
| Next | Break the story into tasks. |
| Last touched | 2026-11-08 |
3. Acceptance
- Every process announces its start and its graceful stop, and telemetry stores the events so the roster tells stopped from lost and counts restarts.
- A service that starts again raises a service restarted notification to the super administrators.
- A service that shuts down gracefully logs out and leaves no open session behind.
- The system-health home shows a services section that summarises the roster and links to the services screen.
4. Tasks
| Task | State | Start | End | Description |
|---|---|---|---|---|
| Record service starts and stops | BACKLOG | Every process announces its start and its graceful stop through the shared service lifecycle; telemetry stores the events, so the roster tells stopped from lost and counts restarts. | ||
| Notify super administrators of service restarts | BACKLOG | Telemetry raises a service-restarted notification to the super administrators when a service starts again, marking a restart whose previous instance never stopped gracefully. | ||
| Close service sessions on shutdown | BACKLOG | A service that logged in as its service account logs out through iam.v1.auth.logout when it shuts down gracefully, so a restart leaves no open session behind. | ||
| Show the services in system health | BACKLOG | The system administrator's home splits System health into sections, one for tenants and one for services; the services section summarises the roster and links to the services screen. |
5. Decisions
- Reviewed on 2026-11-08 at sprint 30 start. Both this story and Record system events in a central event log publish service starts and stops. Build the lifecycle events on the central event log once, and do not build them twice.