SolarWinds raises the alert. Halo raises the incident.
Halo's native SolarWinds Orion integration turns network and infrastructure alerts into fully-formed Halo incidents — automatically assigned, prioritised, and linked to the affected asset. No manual triage. No missed alerts.
✓ Alert-to-incident automation✓ Auto-assign to agent or team✓ Asset linked automatically✓ Auto-resolve when alert clears✓ Acknowledge alerts from Halo✓ Native — included in every licence
What you get
From alert to incident in seconds.
When SolarWinds Orion detects a problem — a node going down, an interface flapping, a threshold breach — Halo creates the incident automatically. Your team responds instead of scrambling to log.
Incident Creation
Alert fires. Ticket appears. No one has to do anything.
Every SolarWinds Orion alert triggers a ticket in Halo automatically via a configured action in Orion. The alert summary and details are passed directly into the ticket — giving your team full context the moment the incident lands in the queue.
✓Incident created from any configured SolarWinds alert
✓Alert summary and detail passed into ticket automatically
✓Ticket type configurable — incidents, service requests, or custom
Smart Routing
Right team. Right agent. Set in the alert, not in the queue.
When you configure alert actions in SolarWinds Orion, you specify exactly which Halo agent and team each alert type routes to. Incidents land in the right place the moment they're created — no manual triage required.
✓Agent specified per alert action in SolarWinds Orion
✓Team specified per alert action in SolarWinds Orion
✓Different alert types can route to different teams
Asset Linking
The affected device linked before an agent opens the ticket.
The alert action passes a unique asset identifier from SolarWinds to Halo. Halo performs a lookup and automatically links the matching asset record to the incident — no hunting around the CMDB.
✓Asset matched via unique identifier from alert payload
✓Full asset history visible directly from the incident
✓Supports problem management — spot repeat offenders fast
The detail
Everything the integration delivers.
The full feature set — active from day one, included in your Halo licence, no middleware required.
Automated incident creation
SolarWinds alert trigger actions post directly to the Halo API, creating an incident automatically — no manual logging, no alert fatigue from email inboxes.
Alert detail in ticket
The alert summary and details from SolarWinds are passed directly into the Halo ticket subject and body at creation time.
Auto-assign to agent or team
Each alert action in SolarWinds Orion specifies the agent and team to assign in Halo. Incidents route to the right person the moment they're created.
Asset linked automatically
A unique identifier in the alert payload is matched against Halo asset records. The correct asset is linked to the incident at creation — no manual lookup needed.
Auto-resolve when alert clears
When SolarWinds fires a reset action, the linked Halo ticket is automatically resolved. Incidents close themselves when the underlying issue is fixed.
Acknowledge alerts from Halo
Agents can acknowledge a SolarWinds alert directly from within the Halo ticket — adding a note to the acknowledgement which is synced back to SolarWinds Orion.
Close ticket = clear alert
Closing a Halo ticket linked to a SolarWinds alert automatically clears the alert in Orion — keeping both platforms in sync without any manual action.
Configurable ticket type
Choose what ticket type incoming SolarWinds alerts create in Halo — incidents, service requests, or any custom type that fits your workflow.
First-party — no extra cost
Built and maintained by Halo's engineering team. Included in your standard Halo licence — no connector fees, no middleware subscriptions, no third-party tools.
Getting connected
How the integration is configured
Setup is split between Halo and SolarWinds Orion. No third-party middleware required — the integration works directly between the two platforms. Allied ESM can scope and configure this as part of your project.
Requires SolarWinds Orion version 2020.2 or later
1
Enable the SolarWinds module in Halo
In Halo, go to Configuration → Integrations and enable the SolarWinds module using the plus icon. Once enabled, open the module settings. Halo will display the trigger and reset action templates — including the API endpoint and authentication details you'll need when configuring SolarWinds Orion.
2
Set up authentication
In the Halo setup screen, enable basic authentication and generate a username and password. These credentials are added to the trigger and reset actions in SolarWinds Orion to authenticate the API calls. Keep the password safe — it is only displayed once at generation time.
3
Configure trigger actions in SolarWinds Orion
In SolarWinds Orion, add a trigger action to each alert you want to feed into Halo. The action posts to the Halo API using the endpoint and credentials from step 2. The action body specifies the ticket summary, details, team, agent, and the asset identifier to link — customised per alert type.
4
Configure reset actions (for auto-resolve)
Add a reset action to each alert in SolarWinds Orion using the reset action template from Halo. When an alert condition clears, Orion fires the reset action and Halo automatically resolves the linked incident — keeping incidents closed the moment the underlying issue is resolved.
5
Configure asset matching in Halo
In Halo, specify which asset field stores the unique identifier that will be passed in the alert payload. When an alert arrives, Halo looks up the matching asset and links it to the new incident automatically.
6
Test and go live
Trigger a test alert from SolarWinds Orion and verify the incident appears in Halo with the correct assignment and linked asset. Confirm a reset action resolves it cleanly. Once validated, the integration is live for every configured alert.
Allied ESM configures this for you
Allied ESM can scope and configure the full Halo + SolarWinds Orion integration — Halo module setup, authentication, SolarWinds alert actions, asset matching configuration, and end-to-end testing. Whether it's part of a new implementation or being added to an existing environment, we'll handle it properly.
Real-world uses
Three ways this changes the day-to-day.
These are the most common ways teams put the Halo + SolarWinds Orion integration to work from go-live.
01
A server goes down at 2am. An incident is already open by the time anyone wakes up.
SolarWinds Orion detects the server is unreachable and fires a Critical alert. The trigger action posts to Halo — an incident is created, assigned to the on-call team, and linked to the server asset. When the on-call engineer checks their phone, the ticket is already waiting with full context. When the server recovers, the reset action fires and Halo resolves the ticket automatically.
Orion alert fires→Incident created→Auto-resolved on recovery
02
Network interface flapping gets caught before it becomes a full outage.
Orion detects a switch port flapping. The trigger action creates a Halo incident with the switch linked from the CMDB. An engineer investigates and resolves the hardware fault before any users are impacted. They acknowledge the SolarWinds alert directly from within the Halo ticket — no need to log into Orion separately.
Warning alert→Incident + asset linked→Acknowledged in Halo
03
Repeat alerts on the same device trigger a Problem record — not just another incident.
The same application server triggers a High CPU alert three times in two weeks. Each alert creates an incident in Halo with the server linked. A service desk manager spots the pattern, links all three incidents to a Problem record, and opens a root cause investigation. The team identifies a poorly optimised batch job, fixes it, and the repeat alerts stop.
Repeat alerts→Pattern spotted→Problem raised
Common questions
Frequently asked questions
Is the SolarWinds Orion integration included in every Halo licence?
Yes. The SolarWinds Orion integration is a native, first-party Halo integration included in the standard monthly licence. There is no middleware, no third-party connector, and no additional subscription required.
Which version of SolarWinds Orion is required?
You must be running SolarWinds Orion version 2020.2 or later. The integration uses alert trigger and reset actions in Orion to post data to the Halo API, which requires this version as a minimum.
Can we control which SolarWinds alerts create Halo incidents?
Yes. You configure trigger actions individually on each alert in SolarWinds Orion. Only alerts with a configured trigger action will create incidents in Halo. This gives you full control over which alerts generate tickets and what information each one passes across.
Does Halo auto-resolve the incident when the SolarWinds alert clears?
Yes. If a reset action is configured on the alert in SolarWinds Orion and the alert condition clears, Orion fires the reset action and Halo automatically resolves the linked incident. This bidirectional behaviour keeps Halo and SolarWinds in sync without any manual intervention.
Can we acknowledge SolarWinds alerts from within Halo?
Yes. When a ticket has been created from a SolarWinds alert, an Acknowledge Alert button appears on the ticket sidebar in Halo. Clicking it opens a prompt to add a note, and the acknowledgement is synced back to SolarWinds Orion. This requires the Halo Integrator to be running on your SolarWinds Orion server. Allied ESM can configure this as part of your setup.
We use SolarWinds alongside other monitoring tools — can Halo handle alerts from multiple sources?
Yes. Halo integrates natively with a wide range of monitoring platforms — including Nagios, Zabbix, PRTG, Datadog, and others — in addition to SolarWinds Orion. All 250+ native integrations are included in the standard licence, so running multiple monitoring sources into a single Halo queue carries no additional cost.
We are already live on Halo — can we add SolarWinds without starting over?
Yes. The SolarWinds Orion integration can be added to any existing live Halo environment. Allied ESM can scope and configure the full setup — Halo module configuration, authentication, SolarWinds alert actions, and asset matching — without disrupting your current workflows.
Ready to turn SolarWinds alerts into Halo incidents?
Allied ESM can scope and configure the full Halo + SolarWinds Orion integration — whether you're starting fresh or adding it to an existing environment. Talk to us to find out what's involved.
