SolarWinds Observability

SolarWinds Observability can notify OpsFusion through its Notification Services webhook, which supports a customizable payload body.

See API Overview for authentication and finding your Account ID/Team ID.

Configure the Webhook in SolarWinds Observability

1. In SolarWinds Observability, go to Settings → Notification Services → Webhook and add a new notification.
2. Set the URL to https://api.opsfusion.cloud/v1/account/YOUR_ACCOUNT_ID/push/alert.
3. Set the authentication to Token (or Basic, if preferred) and supply your OpsFusion API key.
4. Enter the JSON body below in the notification’s payload field.
5. Use the built-in Notification Test button to confirm delivery before relying on it.

Payload Template

{
  "teamId": YOUR_TEAM_ID,
  "title": "{{name}}",
  "description": "{{condition}}",
  "severity": 2,
  "status": 1,
  "labels": {
    "triggerId": "{{triggerId}}"
  }
}

Variables use double curly braces ({{name}}), not a percent-sign format. Common fields across alert types include {{type}}, {{name}}, {{severity}}, {{priority}}, {{condition}}, and {{triggerId}}; metric, log, and anomaly alerts each add their own extra fields (e.g. {{#metrics}}/{{#affectedEvaluations}} blocks for metric alerts, {{recordCount}}/{{query}} for log alerts) — check the variable picker in your specific notification type for the full list.

The body field only supports Mustache-style “render if present” sections (e.g. {{^numberOfAdditionalEntities}}None{{/numberOfAdditionalEntities}} as a default-value fallback) — there’s no documented true if/else branching, so status can’t be computed inline from a single field the way it can with tools like Datadog or New Relic. SolarWinds Observability’s other native integrations (e.g. OpsGenie, PagerDuty) use separate “trigger” and “reset” notification configs for this same reason — set up the same way here: one notification config per state, each with status hardcoded.

Field Mapping

OpsFusion field	SolarWinds Observability source
teamId	Hardcoded per notification
title	{{name}}
description	{{condition}}
severity	Hardcoded per notification, or mapped from {{severity}}/{{priority}} if you prefer a per-notification override
status	Hardcoded per notification — one config bound to the trigger condition (1), a separate one bound to the reset/cleared condition (3)
labels	{{triggerId}}, or any other variable exposed for your alert type

Troubleshooting

• Placeholder shows up literally in the title/description instead of the real value: the variable name is likely wrong for this alert type, or uses single braces/percent signs instead of {{double curly}} — use the notification editor’s variable picker rather than typing names from memory.
• Nothing arrives at OpsFusion: use the Notification Test button first to confirm the webhook URL and auth are reachable, independent of any real alert firing.
• Alerts never resolve in OpsFusion: confirm you have a second notification configured for the reset/cleared condition with status: 3 — a single notification config can’t branch on state inline.
• Confused this with SolarWinds’ on-call product: if you’re actually trying to migrate away from SolarWinds Incident Response (formerly Squadcast) rather than send it monitoring data, see OpsFusion vs SolarWinds Incident Response instead.

Support

For integration support:

• Email: support@opsfusion.cloud
• See Send Alerts for the full API reference