tdanner ✭✭✭✭✭

Also... The Universal Device Poller application talks to the Module Engine, which talks to the Job Scheduler, which talks to the Job Engine. All on port 17777. This works thanks to Microsoft's Net.Tcp Port Sharing Service.

Try adding this to the WHERE clause: AND Nodes.Uri NOT IN ( SELECT S.EntityUri FROM Orion.AlertSuppression S WHERE S.SuppressFrom < GETUTCDATE() AND (S.SuppressUntil IS NULL OR S.SuppressUntil > GETUTCDATE()) )

Thanks for sharing! As a shortcut, Orion.Nodes has a "DetailsUrl" property you can use instead of '/Orion/NetPerfMon/NodeDetails.aspx?NetObject=N%3a' + ToString(Nodes.NodeID)

No known issues with this.

Can you describe what you are seeing in more detail?

If you have read the information on GitHub and are looking for more, you could try the "Create Custom SLA Reports with SWQL" class in the "Virtual Classrooms" section of the customer portal. Virtual Classrooms | SolarWinds Customer Portal​. Unfortunately that interface does not support linking to particular classes so you…

Suggestion: after attempting to unmanage and application from a script, try querying the UnmanageFrom/UnmanageUntil properties of that application and see if they match what the script tried to set them to. This might give a clue as to what is going on here.

This is fixed in Orion Platform 2018.2 / NPM 12.3, out today.

The NCM account limitation issue is still open. The issue tracker shows that the flow navigator account limitation issue was resolved in NPM 11.5.2. If you are still seeing this kind of issue with NTA in that version or later, please let me know.

Please let us know - in this forum or via support - if you are are seeing other gaps in limitations.

Here's what the SDK doc says about SWIS v2 and v3: SWIS Version 3 and 2 Orion Platform version 2012.1, shipped with Orion NPM 10.3, introduces a new version of the SolarWinds Information Service, denoted as version 3 or SWISv3. It runs along with the original version of SWIS (denoted as SWISv2), which is planned to be…

<%if (!string.IsNullOrEmpty(SolarWinds.Orion.Web.DAL.WebSettingsDAL.SiteLoginText)) { %> <marquee id="SiteLoginText"><%=SolarWinds.Orion.Web.DAL.WebSettingsDAL.SiteLoginText%></marquee> <% } %>

Also, I don't know what data you are looking for. This may not be it. This entity is a real-time view of the local Windows Performance Counters of the Orion server itself. If you are looking for the performance data that Orion has collected from the monitored nodes, that's in other entities. If you can tell me more about…

Yes, but why? Is there some reason these reports can't be created through the GUI?

The "Availability Statistics" resource on the Node Details view gets its data by rolling up the Availability column in the Orion.ResponseTime entity. There are two modes that can be used to compute Availability, documented here: Calculating Node Availability

In Advanced Alert actions you can get the scaled (Mbps) value by using a variable like this: ${Inbps as Bandwidth} instead of ${Inbps}.

Please start a new thread for this issue and post the query that triggered the error.

The verb just updates one IP. You have a list of them to update, so you can call the verb in a loop. Like this: $IPList = Get-Content -Path C:\.IP.txt foreach ($ip in $IPList) { Invoke-SwisVerb $swis IPAM.SubnetManagement ChangeIPStatus @($ip, "Used") }

Add-PSSnapin : No snap-ins have been registered for Windows PowerShell version 5. PowerShell snapin registration is separate for 32-bit and 64-bit shells. The installer should have registered both, but apparently it failed. When you register it manually, run both versions of installutil.exe.…

Good request. I captured this as CORE-8445. The single character wild card is already supported - just use the underscore '_' to match any one character in a LIKE pattern. Same as T-SQL.

To send a multi-valued parameter for use with a WHERE x IN (...)-style query, encode the value as a JSON array, like this: { "query": "SELECT NodeID, Caption FROM Orion.Nodes WHERE NodeID IN @ids", "parameters": { "ids": [2,4,6] } } I just added this example to the https://github.com/solarwinds/OrionSDK/wiki/REST page as…

PollNow expects a "net object id". For nodes, that looks like this: "N:123" If you have a NodeID, you need to prefix it with "N:". In PowerShell, try this: Invoke-SwisVerb $swis "Orion.Nodes" "PollNow" @( "N:$NodeID" )

Answered here: Interfaces Custom Properties URI is NULL

The intention is for the wiki to replace all the parts of the pdf that are worth keeping. I deliberately skipped the SOAP-related information. The SOAP endpoint for SWIS is not going away, but I am trying to steer new users to either the JSON or PowerShell methods. SOAP has proved very troublesome to support. Could I ask…

Nothing dramatic has changed other than the distribution model. You can see some notes on the Releases page: Releases · solarwinds/OrionSDK · GitHub and more detail if you look at the commit log: Commits · solarwinds/OrionSDK · GitHub.

Could you clarify what you mean by "SLA"? Also, you might find this kind of thing easier to do if you define groups for these subsets of nodes. Like have one group with filters for Application-1234 AND production and another group for Application-1234 AND dev. Then your group report would only need to select the right set…

Please start a new thread for your question. This one is already long and contains many unrelated discussions.

I tried it and I get a different error: 2018-08-24 13:35:59,384 [26] ERROR AlertingLogger - (null) Failed to execute an HTTP request. Method: POST, Url: https://xxxxxxx:17778/SolarWinds/InformationService/v3/Json/Invoke/Orion.Nodes/Remanage, Body: ["N:4"]) System.Net.WebException: The underlying connection was closed:…

The response is a JSON value (a string quoted according to JSON rules), though not a JSON object.

I'd like to help you, but I can't tell what you are asking. Have you tried the samples from https://github.com/solarwinds/OrionSDK/tree/master/Samples ?