docs(roadmap): say what #91 still needs, now that the exporter exists - #198
Merged
Conversation
The entry read "Add blackbox-exporter for uptime and TLS-expiry on internal services. Until it exists, expiry is something you find out about from a browser warning." The exporter has existed for a while: compose.yaml defines it, prometheus.yaml scrapes it and runs the blackbox job, and there are targets. But "add the exporter" was never the work. #91 named seven things to probe — Grafana, Prometheus, Alertmanager, Loki, the switch UI, the iLO, the pfSense UI — and none of them are probed. What is probed is the wiki, which the issue never mentioned; it was added later, after the wiki went unreachable and nothing noticed. So the entry was stale in the direction that flatters: it implied nothing had shipped, when what shipped was aimed elsewhere. The expiry half has nothing behind it. Both targets are plain HTTP, the TLS-capable http_2xx module is defined and referenced by nothing, and no rule under prometheus/rules/ reads probe_ssl_earliest_cert_expiry — grepped for ssl, cert, expiry and expir across all six rule files, no hits. Grafana is the only service in the estate terminating TLS and it is not a blackbox target, so there is not even a series to alert on. Nothing moves to Done. This file's own intro says whether a thing is started, blocked or done belongs on its issue, and that "two places holding the same checkbox is how a checkbox stops being true" — #91 is open, so a Done entry for half of it is the failure that warning describes. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This was referenced Aug 31, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
docs/roadmap.md:52-54read:The exporter has existed for a while —
compose.yaml:258-279defines it,prometheus.yaml:55-57,105-123scrapes it and runs theblackboxjob, andtargets/blackbox.yamlhas targets."Add the exporter" was never the work
This is the part worth flagging. #91 names seven things to probe — Grafana, Prometheus, Alertmanager, Loki, the switch management UI, the iLO, the pfSense web UI. None of them are probed.
What is probed is the wiki, twice, which the issue never mentions. It was added later, after the wiki went unreachable unnoticed (
blackbox/blackbox.yaml:5-8). So the old entry was stale in the flattering direction: it implied nothing had shipped, when the truth is something shipped and it was aimed somewhere else entirely.The expiry half has nothing behind it
Verified rather than assumed:
ssl,cert,expiry,expiracross all six files inprometheus/rules/: zero hits, so noprobe_ssl_earliest_cert_expiry.targets/blackbox.yamlusehttp_2xx_plainagainsthttp://URLs.http_2xxis defined inblackbox/blackbox.yaml:27-42and referenced by nothing.Nothing moved to Done
You asked me to check. I don't think anything should, and the file argues it better than I can — its own intro:
#91 is open. A Done entry for half of it is precisely the failure that warning describes.
Verification
make validatepasses — including "documents agree with the configs", which does not readroadmap.md(no docs-checker references it), so this was never going to be caught mechanically.Context: found while fixing #74 (stale documentation claims), deliberately left out of #196.
🤖 Generated with Claude Code