Description
26.7 stops the NetFlow service before config reloads, so brief flow-export gaps are now expected behaviour on config changes. Review internal/flow gap handling and any Grafana alert thresholds keyed on flow arrival so a config reload does not page; document the expectation in docs/flow.md.
Acceptance Criteria
- #1 Config-reload-length flow gaps do not fire alerts; behaviour documented
Definition of Done
- #1 just check
- #2 just gen (if any generated artifact changed) and the diff committed
Implementation Plan
Wave 2 L11: inspect current NetFlow gap metrics and alert thresholds, establish whether a configuration-reload-length restart can page, document the expected 26.7 restart gap, and change no runtime or alert logic unless the existing threshold is demonstrably unsafe. Documentation-only lane.
Final Summary
Documented the expected OPNsense 26.7 NetFlow restart gap and proved from the existing rule contract that OPNsenseNetFlowHookDead requires 45 minutes of silence plus traffic evidence and a 5-minute hold, so a reload-length gap cannot page. Landed in commit e0309efc. Verified with just docs-check </dev/null: doclint passed and all generated docs were current. CodeRabbit was deliberately skipped because this was documentation-only.