Goal
Formalize the boundary between the vendor-neutral monitoring core and optional router-specific telemetry before adding more router vendors.
The current FRITZ!Box integration proves the concept, but the next step should be a small, explicit adapter contract rather than copying vendor conditionals into the core.
Proposed telemetry surface
An adapter should expose optional fields/events such as:
- router model / firmware
- router uptime
- WAN state
- WAN-session uptime
- WAN transport
- WAN/public IP when available
- last WAN error when available
- vendor event/log context around an incident
The generic core must continue to work when an adapter is absent or temporarily fails.
Acceptance criteria
- define the smallest useful adapter interface/data model
- move FRITZ-specific access behind that boundary without changing generic behavior
- preserve graceful degradation when vendor telemetry fails
- add unit tests around adapter success/failure/partial telemetry
- document how a future adapter should be implemented
This is a prerequisite for treating OpenWrt, MikroTik or UniFi integrations as first-class roadmap work.
Goal
Formalize the boundary between the vendor-neutral monitoring core and optional router-specific telemetry before adding more router vendors.
The current FRITZ!Box integration proves the concept, but the next step should be a small, explicit adapter contract rather than copying vendor conditionals into the core.
Proposed telemetry surface
An adapter should expose optional fields/events such as:
The generic core must continue to work when an adapter is absent or temporarily fails.
Acceptance criteria
This is a prerequisite for treating OpenWrt, MikroTik or UniFi integrations as first-class roadmap work.