Skip to main content

SolarWinds Integration with Network Copilot Enables Enhanced Network Insights

November 20, 2025

SolarWinds has announced an integration between its Orion platform and Network Copilot, which enables a transformation of Orion from a Standalone (SA) monitoring tool into an interactive layer of real-time network intelligence. This integration aims to provide enterprise IT leaders with seamless access to previously siloed telemetry data.

Integration Overview

The integration addresses significant challenges faced by network operators, including siloed access, manual data sharing, and limited real-time insights. By utilizing the SolarWinds Information Service (SWIS) Application Programming Interface (API) in tandem with Kafka streaming, the integration facilitates the delivery of structured and queryable insights across device inventories and performance metrics within Copilot.

Mechanics of the Integration

The SolarWinds Collector for Copilot acts as a bridge between the restricted data environment of Orion and the open platform of Copilot. It extracts and normalizes data using the SWIS API, then streams it into Kafka, enhancing the availability of SolarWinds data across the Copilot platform.

Features of the Collector

This solution is designed as a containerized microservice that operates alongside existing data collectors. It performs scheduled queries at customizable intervals to ensure up-to-date data is available for analysis. Notable characteristics include:

  • A containerized architecture that integrates smoothly with other collectors.
  • Secure access via SWIS API, eliminating the need for direct database access.
  • Regular polling of inventory and performance data to maintain freshness.
  • Schema normalization for uniformity of data across the platform.
  • Live data streaming to Copilot.

Data Coverage of the SolarWinds Collector

The collector queries various entities within the Orion database to provide comprehensive visibility into static and dynamic information about devices, interfaces, and performance metrics.

Device Inventory

Information is obtained from Orion databases to construct detailed profiles for each device, which includes:

  • IP address, hostname, model, vendor, and uptime status.
  • Classification and Operating System (OS) details.

Interface Inventory

Network Performance Monitor (NPM) interfaces are accessed to obtain:

  • Interface name, status, and metrics such as speed and MTU.

Hardware Metrics

Data regarding hardware components such as fans and power supplies is also retrieved, which covers:

  • Model, serial numbers, and operational status.

Performance Metrics

Real-time performance data is taken from core entities like Central Processing Unit (CPU) load and interface counters, providing:

  • Current traffic metrics and error rates.

Operational Workflow in Copilot

The collector securely authenticates against SolarWinds, retrieving and converting data into JSON format which is then transmitted into Kafka topics, ensuring smooth integration into Copilot's data model.

  • Authentication is managed through the Orion Software Development Kit (SDK) using predefined credentials.
  • The collector operates as a containerized service to ensure efficiency.
  • Data is converted and streamed into a unified model for operational consistency.

Advantages for Users

The integration offers enhanced data accessibility leading to accelerated troubleshooting and deeper insights into device performance in real-time. This is achieved through user-friendly querying within Copilot.

Operational Efficacy

Network personnel can evaluate device reachability and status without needing to access the Orion UI. Example prompts facilitate communication with the system, allowing for straightforward inquiries regarding device performance.

Visibility for Hardware Management

Detailed asset data aids in audits and lifecycle planning by allowing direct access to organizational hardware records through simple queries.

Performance Monitoring

Live telemetry allows operators to monitor CPU and memory usage proactively, ensuring effective management of network resources.

Conclusion

This integration marks a transition for SolarWinds Orion from a monitoring silo to a source of actionable intelligence within the Network Copilot platform. The changes eliminate data access problems and hasten the process of monitoring network health.

Related Perspectives