EXTENSIONS

Event topology observation — discovers the directed graph of event

Unified drift detection surface that composes observations from existing

Structural health monitoring for a UniFi fabric. The `@sntxrr/unifi-fabric/topology` model's `check` method compares a declared topology against live `/stat/device` rows and reports the failures that outcome-based monitoring cannot see: a device expected on the wire that has silently fallen back to a wireless mesh uplink, attachment to the wrong upstream device, links negotiated below their expected speed, ports carrying error counters, and — the one with no equivalent elsewhere — ports that are down but have carried real traffic before, which identifies a run that used to work. The first three are detectors and gate `inSync`; error counters and dark ports are cumulative totals rather than rates, so both are reported as diagnostics and deliberately do not, since a single snapshot cannot tell a severed run from a client that went to sleep. An access point that loses its wired uplink does not fail; it meshes, keeps serving clients, and every uptime check stays green while latency quietly goes from sub-millisecond to tens of milliseconds and jittery. `uplink.type` flipping from `wire` to `wireless` is a boolean, so it is asserted exactly rather than thresholded. Read-only: never writes to the controller. Emits a flat Prometheus-ready metric series alongside the verdict, including for healthy devices, so alerts can fire on a series dropping to zero rather than on a document changing shape. Authenticates with an API key over `X-API-KEY`, which sidesteps the HTTP 499 that MFA-enabled SSO accounts return for password logins.

Region-wide AWS topology discovery and an animated D3 architecture diagram. Adds a fan-out `discover` method to the official @swamp/aws EC2, ECS and ELBv2 model types, then renders every compute object and every inbound and outbound network route into a single self-contained HTML file.

Read-only FreeIPA domain inspection over the JSON-RPC API: realm/config, server inventory, and replication topology, plus a markdown + Mermaid summary report.

Full sceptre-phenix control via the HTTP API, split into six models — config, experiment, scorch, vm, cluster and user: config CRUD (Topology/Scenario/Experiment/Image/User), the experiment lifecycle (create/start/stop/delete, schedule, apps, topology, files, trigger), scorch run control (start, poll-to-completion, status, cancel, output tarballs), VM control (inventory, reconfigure, power, snapshots, captures, commit), and cluster/server reads (hosts, disks, apps, topologies, version, features, settings) plus identity (users, roles, long-lived tokens).