Skip to content

feat(observability): the eeros answer ping, so probe them (ADR-0112) - #1397

Merged
Gerrrt merged 3 commits into
mainfrom
gerrrt/eero-ping-in-force
Nov 11, 2026
Merged

Gerrrt merged 3 commits into
mainfrom
gerrrt/eero-ping-in-force

Conversation

@Gerrrt

@Gerrrt Gerrrt commented Nov 11, 2026

Copy link
Copy Markdown
Owner

What changed

Uncomments the eight eero targets in targets/blackbox-eero.yaml, so prometheus pings each unit every minute and EeroUnreachable can fire. network.md, security.md, observability.md and 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 from 10.0.99.20 on ICMP echoreq, above the Block access to … rows. ping -c3 from prometheus got an answer from 10.0.50.11, 10.0.20.11 and 10.0.10.11. That settles whether an eero answers an echo at all, so ADR-0112 stands and is not superseded.

Blast radius

prometheus only. It converges on main hourly, 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 to default, never to urgent; validate.sh pins that route. Glance's Estate and Uptime widgets will list the eight units.

  • No change to network segmentation or firewall rules. Not ticked: this PR records a new pfSense row into Hicks, Skids and Degens, created by hand today. It is host- and protocol-scoped, as ADR-0112 decided.
  • No new port published to a VLAN that could not already reach the service
  • No credential added outside secrets/*.sops.yaml

Verification

  • The ping: run by hand from prometheus against 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, including promtool check config and test rules for 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 validate passes

  • Deployed 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, or docs/roadmap.md)

🤖 Generated with Claude Code

Copilot AI balanced review requested due to automatic review settings November 11, 2026 03:55
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>

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 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
Gerrrt enabled auto-merge (squash) November 11, 2026 03:58
@Gerrrt
Gerrrt merged commit ed9a7ed into main Nov 11, 2026
8 checks passed
@Gerrrt
Gerrrt deleted the gerrrt/eero-ping-in-force branch November 11, 2026 04:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants