Skip to main content

Integrating SolarWinds Orion with Faddom

Written by Egor Marachev

Note: This integration is available from Faddom v2026.3.

Faddom’s events integration with SolarWinds Orion sends alert triggers and resets from the SolarWinds Platform (Orion) directly into Faddom, so infrastructure events surface alongside your topology data. One integration covers every Orion module that uses the SolarWinds alerting engine.

This article guides you through setting up the integration, adding the optional daily sync, and troubleshooting common issues.

Prerequisites

Before you begin, make sure you have the following:

  • Administrator access to Faddom

  • Access to SolarWinds with permission to manage alerts

  • A Faddom API access token. See Creating the API Token for API Access if you don’t already have one

  • Network access from the SolarWinds server to the Faddom UI endpoint (typically port 443 or 9443)

  • SolarWinds must accept Faddom’s HTTPS certificate (see Allowing SolarWinds to accept Faddom’s certificate)

  • For the optional sync: network access from the Faddom proxy to the SolarWinds server on port 17774

Setting up the integration

The setup starts in Faddom, where the integration generates a preconfigured alert definition, and continues in SolarWinds, where you import and configure it.

In Faddom

Follow the steps below to create the integration and download the alert definition.

Step by step:

  1. Go to Settings > Events Integrations and click Add Integration.

  2. Enter a unique name (such as “SolarWinds Events”), select SolarWinds as the type, and click Apply. [Image: A screenshot of the new integration modal with the name and type fields filled in.]

  3. Get your access token using the link in the integration details panel.

  4. Download the preconfigured Faddom alert definition, faddom_solarwinds_alert.xml. [Image: A screenshot of the “Next Steps” panel in the integration details, highlighting the faddom_solarwinds_alert.xml download link.]

In SolarWinds

Follow the steps below to import and activate the Faddom alert.

Step by step:

  1. Go to Alerts & Activity > Alerts > Manage Alerts > Export/Import > Import Alert and select the downloaded XML file.

  2. Edit the imported alert, “Faddom Events - <integration name>“, and set the trigger condition to the event type it should report, along with its severity and scope. The template ships with a node-down condition as an example.

  3. Attach your Faddom access token to both actions, the trigger action and the reset action:

    • Authentication: Token

    • Header name: Authorization, value: Bearer <your access token>

  4. Allow SolarWinds to accept Faddom’s HTTPS certificate (see Allowing SolarWinds to accept Faddom’s certificate).

  5. Enable the alert (it is imported as disabled) and submit.

Every alert trigger now opens an event in Faddom on the matching server, and every reset closes it. To report more event types, duplicate the imported alert in Manage Alerts and give each copy its own condition and severity.

Note: Faddom matches each alert to a server by the node’s IP address or hostname. Alerts on objects that don’t correspond to a server Faddom knows are skipped.

Allowing SolarWinds to accept Faddom’s certificate

SolarWinds checks Faddom’s HTTPS certificate before it sends events. What to do depends on the certificate Faddom uses:

  • A certificate from your organization’s CA: no action is needed, as long as the SolarWinds server trusts that CA.

  • The default Faddom certificate: change the SolarWinds advanced settings, as described below.

To change the advanced settings, follow these steps:

  1. Open <SolarWinds URL>/Orion/Admin/AdvancedConfiguration/Global.aspx.

  2. Clear SendHttpRequestCheckOnCertificateChainErrors and SendHttpRequestCheckOnCertificateNameMismatch.

  3. Click Save.

  4. Restart the SolarWinds Orion Module Engine service.

Note: These settings apply to all HTTP request actions in SolarWinds.

Setting up the sync (optional)

The webhook above works on its own. The sync adds a daily pull that catches up on anything the webhook missed, such as events fired while Faddom was restarting.

Follow the steps below to enable the sync.

Step by step:

  1. Create a dedicated SolarWinds account for Faddom: a standard user with no administrator rights and no account limitations. The sync authenticates with a username and password; a SolarWinds API token can’t be used here.

  2. In the Faddom integration details panel, expand Sync (SWIS) - optional.

  3. Enter the SWIS host (usually your main SolarWinds server), the username, and the password. Credentials are stored encrypted.

  4. If your SolarWinds server uses a self-signed certificate, check Ignore SSL certificate errors.

  5. Click Save sync settings. Faddom validates the connection before saving; this can take up to a minute. [Image: A screenshot of the expanded “Sync (SWIS) - optional” section with the SWIS host, username, and password fields filled in.]

Troubleshooting

If events don’t appear in Faddom, work through the following checks:

  • Confirm the imported alert is enabled and its condition currently matches at least one object.

  • Test the integration with a real alert. A manual Execute sends an empty alert ID, so it fails even when the setup is correct.

  • “Failed to execute HTTP request” on the action usually means SolarWinds doesn’t accept Faddom’s HTTPS certificate. See Allowing SolarWinds to accept Faddom’s certificate.

  • Confirm the Authorization header is set on both actions, with the value in the form Bearer <token>.

  • Confirm the alerted object resolves to a server that exists in Faddom.

  • For the sync: confirm the Faddom proxy can reach the SolarWinds server on port 17774.

If you have any questions or need help please let us know by contacting support@faddom.com.

Related Articles
Did this answer your question?