Built 7 read‑only host reporting roles
Built seven read‑only reporting roles that render a live host to
Markdown — facts, access, git, metrics, traffic, security and
provider inventory — under a rule that no number is printed the run
did not measure.
September 2026

Situation. The host had no dashboard and was not getting one,
because a metrics stack does not fit on 464 MB and would not have
been worth its cost if it did. That left an honest gap: there was no
way to answer questions like who has access, how much has this
repository grown, what does the traffic look like, or is the
hardening actually enforced.

Task. Those questions needed answers that could be produced on
demand, cost the host nothing while nobody was asking, and could
never change the thing they were describing.

Action. Seven read‑only roles, each rendering a live host into
Markdown in the repository. A facts snapshot covering operating
system, hardware, storage, network, services, packages, listening
sockets and processor utilisation computed from two samples of the
kernel's own counter. An access report covering accounts, sudo
scope, key fingerprints, forge users and database roles. A git
report per repository. A metrics report over the day's collected
samples. A traffic report built from the web server's privacy‑masked
log. A provider inventory across four provider surfaces — DNS, two
cloud APIs and a dedicated‑server API. And a security report that
answers whether hardening is enforced rather than configured,
printing the firewall rules in match order and the live ban rule
set. The governing rule across all seven is that no number is
printed that the run did not measure — a report that fills a gap
with a plausible figure is worse than one that leaves it blank,
because only the plausible one gets believed.

Result. The estate can be described from the repository on demand,
and the reports have found real things: the two dead security
controls, an undeclared listening port, and the observation that the
traffic archive is only as old as the last time somebody remembered
to harvest it. That last one is written up as a limitation with a
specific cost recorded — sixteen days of one site's history that
rotated away between harvests and do not exist anywhere.

Categories:
1Infrastructure	/categories/infrastructure/	platform.engineer.company	70
1Automation & CI/CD	/categories/automation/	platform.engineer.company	70
1Monitoring & Observability	/categories/observability/	platform.engineer.company	70
1Linux & Servers	/categories/linux/	platform.engineer.company	70
1Stakeholder & Reporting	/categories/stakeholder/	platform.engineer.company	70
1Documentation	/categories/documentation/	platform.engineer.company	70

Services:
1Site Reliability & Monitoring	/services/site-reliability/	platform.engineer.company	70
1System Administration	/services/system-administration/	platform.engineer.company	70
1Technical Documentation	/services/technical-documentation/	platform.engineer.company	70

hThis page on the web	URL:https://platform.engineer.company/portfolio/built-7-read-only-host-reporting-roles/	platform.engineer.company	70
