Routing Neighbor Alert Delay Due to Polling Interval in SolarWinds Observability SaaS

You may find that a Routing Neighbor alert is configured correctly but does not fire immediately when a neighbor goes down. It may also take several minutes for the Routing Neighbor status to refresh after the state changes.

You may be more likely to notice this during migration from SolarWinds NPM if you previously experienced faster routing-neighbor alerting in a different monitoring workflow.

Routing Neighbor state changes are reflected after the next polling cycle. Because the default polling interval is 5 minutes, alert evaluation can be delayed until the updated state is collected and processed. At this time, there is no UI option to reduce the polling interval specifically for the Routing Neighbor entity. Any interval change applies more broadly at the collector level rather than only to Routing Neighbor.

Allow up to one poll cycle for Routing Neighbor status to update after a change occurs. If a shorter polling interval is required, you can change the interval at the network collector level by updating the EntityWorker.ExecutionInterval setting. This change applies globally to all entities handled by that collector, not only Routing Neighbor.

The exact file path may vary based on the Network Collector version in your environment. To help preserve this setting after an update, add the override to appsettings.local.json in the Network Collector plugin directory instead of changing only the base appsettings.json file.

Example configuration:

{
  "EntityWorker": {
    "ExecutionInterval": "00:05:00"
  }
}