Documentation
SolarWinds
Connecting REAP to SolarWinds (opens in a new tab): prerequisites, permissions, setup, what is read and written, troubleshooting.
Overview
Planned, not available today: REAP would read SolarWinds (opens in a new tab) alerts and metrics as evidence; it does not modify monitoring. Today, incidents SolarWinds raises in ServiceNow (opens in a new tab) or Jira (opens in a new tab) reach REAP through the ITSM; prioritization of third-party alert streams is in development.
Status Planned Not available today and without a date. The sections below describe the design, so a reviewer can see what the integration would read and write; tell us if you need it.
Prerequisites
- SolarWinds Platform (opens in a new tab) (Orion) with the SWIS API reachable from the platform or connector which component connects
- Read-only account
Permissions requested
| Scope | Permission | Why |
|---|---|---|
| Read | Alerts, nodes, interfaces, metrics via SWIS | Evidence and prioritization |
Setup
- Create a read-only SolarWinds (opens in a new tab) account.
- In REAP: Integrations → SolarWinds (opens in a new tab) → server, credentials; select node groups in scope.
- Test: recent alerts appear as evidence on a device.
What REAP reads
- Active and historical alerts, node and interface status, key metrics
What REAP writes
- Nothing
Troubleshooting
| Symptom | Likely cause | Check |
|---|---|---|
| No alerts | Account lacks alert view rights | Check account limitations |
| High API load | Poll interval too aggressive | Adjust interval |
Changelog
- September 2026 · page created (draft).
Engineering to confirm
- Whether SolarWinds (opens in a new tab) is polled from the connector or the platform
Last reviewed: October 7, 2026 (draft) · Owner: solutions engineering · Corrections: security@reapnet.ai