net-change-detection

To correlate network changes with an incident, identify recent infrastructure modifications and rank them by time overlap and scope relevance across affected devices, firmware, and configuration. This surfaces high-priority leads for faster incident diagnosis.

Detecting infrastructure changes after maintenance involves scanning a specified time window to find configuration or firmware modifications. Ranking these changes by time overlap and scope relevance helps isolate the anomaly explaining degraded network performance.

Yes, network change detection applies to site- or device-scoped investigations. You can provide optional identifiers to narrow the scope, ensuring the analysis targets only the configuration and firmware changes relevant to the affected assets.

Yes, the nettools-core library is a required dependency for network change detection. The skill relies on the bundled NETTOOLS helper and this core library to query network state and output a structured result to stdout.

Ranking changes by time overlap prioritizes infrastructure modifications occurring closest to the incident window. This correlation mechanism filters out irrelevant noise, surfacing only the high-priority configuration or firmware changes that likely triggered the anomaly.

Avoid automated change detection when investigating issues outside a specific time window or lacking defined site and device scopes. The tool relies on time-bounded incident windows and scoped identifiers to accurately rank configuration and firmware changes.