Repository navigation
feat(observability): the eeros answer ping, so probe them (ADR-0112) - #1397
Merged
Merged
Conversation
The Winterfell row ADR-0112 decided exists since 2026-11-11: alias `eeros` and a pass from 10.0.99.20 on ICMP echoreq, above the Block access rows. `ping -c3` from prometheus got an answer from an eero on Hicks, Skids and Degens, so the eight blackbox-eero targets are uncommented. network.md, security.md, observability.md and the Home Assistant package carry the row as in force, Winterfell's Reaches cell names the ping, and the changelog has the day's entry. Refs #1228 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Gerrrt
force-pushed
the
gerrrt/eero-ping-in-force
branch
from
November 11, 2026 03:55
ba8df5b to
1e15a8f
Compare
There was a problem hiding this comment.
🟢 Approval recommended
No active review issues are recorded for the change enabling the eight eero ICMP monitoring targets.
No open issues 🎉
What changed in this PR
Enables the eight eero ICMP targets planned in ADR-0112 now that the required firewall pass exists and one eero per segment has answered ping. This activates the existing minute-level monitoring and warning alert; verification of all eight probes remains pending deployment.
Changes:
- Enables eero targets across Hicks, Skids and Degens.
- Updates current-state documentation and Home Assistant comments to record the firewall pass as active.
- Adds a changelog entry covering the ping checks and remaining deployment verification.
| File | Description |
|---|---|
stacks/sensitive/home-assistant/packages/eero.yaml |
Updates comments only to reflect the active firewall pass. |
stacks/observability/prometheus/targets/blackbox-eero.yaml |
Enables all eight targets and updates firewall guidance. |
docs/security.md |
Records the scoped ICMP pass as active. |
docs/observability.md |
Updates the eero monitoring description. |
docs/network.md |
Records the active pass, ping checks and reachability. |
docs/changelog.md |
Documents activation and the pending all-target check. |
Review effort: Balanced
Gerrrt
enabled auto-merge (squash)
November 11, 2026 03:58
…orce # Conflicts: # docs/changelog.md
…eero-ping-in-force # Conflicts: # docs/changelog.md
3 of 4 tasks
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
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.
What changed
Uncomments the eight eero targets in
targets/blackbox-eero.yaml, soprometheuspings each unit every minute andEeroUnreachablecan fire.network.md,security.md,observability.mdand the Home Assistant eero package now say the Winterfell row is in force since 2026-11-11. Winterfell's Reaches cell names the ping, and the changelog has the day's entry.Why
Refs #1228. This is the third of the four post-merge steps #1384 listed. The row ADR-0112 decided now exists in pfSense: alias
eeros(the eight reservations) and a pass from10.0.99.20on ICMPechoreq, above the Block access to … rows.ping -c3fromprometheusgot an answer from10.0.50.11,10.0.20.11and10.0.10.11. That settles whether an eero answers an echo at all, so ADR-0112 stands and is not superseded.Blast radius
prometheusonly. It converges onmainhourly, and the target file is hot-reloaded within five minutes with no restart. If a unit does not answer, the result is a warning that routes todefault, never tourgent;validate.shpins that route. Glance's Estate and Uptime widgets will list the eight units.secrets/*.sops.yamlVerification
The ping: run by hand from
prometheusagainst one eero per segment. All three replied. The other five addresses were not pinged by hand; the probe covers them once deployed.check_docs.py: docs OK, 160 Prometheus + 21 Loki rules, 12 assertions.lint.sh: passed, with ruff (×2) and ansible-lint skipped as unavailable. yamllint was run separately in a container on the two changed YAML files and was clean.make validate: all checks passed, includingpromtool check configandtest rulesfor observability. Skipped as unavailable or not this host: yamllint, ruff (×2), ansible-lint, the offsite-backup tmpfs case, and the deployment-checkout unit, timer and installed-copy checks.make validatepassesDeployed to the lab and confirmed working. After merge and convergence,
probe_success{job="blackbox-eero"}should read 1 for all eight. Home Assistant: eero units' status from the DHCP lease logs, after reservations #1228 closes after that check.Docs updated (
docs/, service README, ordocs/roadmap.md)🤖 Generated with Claude Code