Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

Orion SDK / SWIS usage thresholds

Hello all,

I would like to ask about SDK/SWIS usage thresholds alias concurrent calls in the same time...

In other words, I will need to add multiple (hundreds) of nodes into maintenance every few moments - like:

Invoke-SwisVerb -SwisConnection $SwisV3 -EntityName Orion.Nodes -Verb Unmanage -Arguments ("N:$($NodeId)", $startTime, $endTime, "false")

And I don't know when it will hit some limit of concurrent calls and block/lock/overutilize the API calls causing failure of the PS script maintenance actions.

Is it somehow related with Orion Swis.Core settings? (MaxConcurrentCallsProcessorMultiplier / MaxConcurrentSessionsProcessorMultiplier)

Unfortunately not much found in Orion / Orion SDK documentation.

Thank you a lot for your help

Find more posts tagged with

sdk

Accepted answers

KMSigma.SWI

The Unmanage verb can only process one object at a time, which is one of the reasons that many people have moved over to the SuppressAlerts verb instead. The SuppressAlerts verb can take an array of URI's to stop the alerting actions. The polling still takes place, but none of the alert actions are fired.

That said, there is no hard and fast limitation on the number of calls to the API. It doesn't have a "fixed" threshold. It's based on how powerful your target server is at handling the calls. And the timeout doesn't apply either, because each call would be short.

On my lab server (way underpowered), it took an average of 283ms per call to call the Unmanage verb for my 27 nodes.

On my lab server (still underpowered), it took a total of 40ms for all 27 nodes.

This is the script I did to test it out:

$SwisConnection = Connect-Swis -Hostname orionweb.kmsigma.local -username 'admin' -Password 'NopeNopeNope'
$ToUnmanage = Get-SwisData -SwisConnection $SwisConnection -Query "SELECT CONCAT('N:', NodeID) AS [NetObjectId] FROM Orion.Nodes WHERE Status <> 9"
$ToUnmanage | ForEach-Object { Measure-Command -Expression { Invoke-SwisVerb -SwisConnection $SwisConnection -EntityName 'Orion.Nodes' -Verb 'Unmanage' -Arguments ( $_, $null, $null, $false ) } | Select-Object -Property Milliseconds }
$ToSuppress = Get-SwisData -SwisConnection $SwisConnection -Query "SELECT NodeID, Uri FROM Orion.Nodes"
Measure-Command -Expression { Invoke-SwisVerb -SwisConnection $SwisConnection -EntityName 'Orion.AlertSuppression' -Verb 'SuppressAlerts' -Arguments ( $ToSuppress.Uri, $null, $null ) } | Select-Object -Property Milliseconds

All comments

KMSigma.SWI

On my lab server (way underpowered), it took an average of 283ms per call to call the Unmanage verb for my 27 nodes.

On my lab server (still underpowered), it took a total of 40ms for all 27 nodes.

This is the script I did to test it out:

$SwisConnection = Connect-Swis -Hostname orionweb.kmsigma.local -username 'admin' -Password 'NopeNopeNope'
$ToUnmanage = Get-SwisData -SwisConnection $SwisConnection -Query "SELECT CONCAT('N:', NodeID) AS [NetObjectId] FROM Orion.Nodes WHERE Status <> 9"
$ToUnmanage | ForEach-Object { Measure-Command -Expression { Invoke-SwisVerb -SwisConnection $SwisConnection -EntityName 'Orion.Nodes' -Verb 'Unmanage' -Arguments ( $_, $null, $null, $false ) } | Select-Object -Property Milliseconds }
$ToSuppress = Get-SwisData -SwisConnection $SwisConnection -Query "SELECT NodeID, Uri FROM Orion.Nodes"
Measure-Command -Expression { Invoke-SwisVerb -SwisConnection $SwisConnection -EntityName 'Orion.AlertSuppression' -Verb 'SuppressAlerts' -Arguments ( $ToSuppress.Uri, $null, $null ) } | Select-Object -Property Milliseconds