Freshness-aware status
Marks an otherwise healthy observation stale when it exceeds the chosen threshold, preventing old results from appearing current.
Day 044 / DevOps / Reliability
Service Health Board
/ Overview
A dependency-free Python CLI that turns a bounded local snapshot into a deterministic service health board with freshness-aware status.
A list of raw service states does not immediately show which observation needs attention, and an old healthy result can be misleading. A useful summary must also avoid copying arbitrary notes or sensitive fields into its output.
/ Provided servicesClear thinking.
Clear thinking.
Practical delivery.
Clear roll-up
Summarizes service rows into a predictable overall state, with down taking priority over degraded, stale and unknown results.
Read-only boundaries
Consumes only a local snapshot, limits input size and record count, omits arbitrary fields and performs no probes, restarts or configuration changes.
/ Solution
Service Health Board validates one bounded local JSON snapshot, calculates observation age with timezone-aware timestamps, classifies each service as healthy, degraded, down, stale or unknown, and produces deterministic text or JSON output. It ignores extra fields and never probes networks, runs service commands, restarts processes or changes infrastructure.
/ Impact
Five explicit health states
Configurable 1–1440 minute freshness threshold
Up to 100 service records
Two-megabyte input boundary
Deterministic name ordering
Extra fields omitted from reports
Text and JSON output
Twelve standard-library tests
Python standard library
Argparse, pathlib, datetime and JSON provide the complete dependency-free command-line workflow.
Defensive data handling
Validates timezone-aware timestamps, service states, unique names, optional latency and strict input limits before reporting.
Unittest
Twelve tests cover status roll-ups, staleness, ordering, privacy boundaries, invalid inputs, file limits and CLI exit behavior.