dan_jagnow · Senior Architect

This issue with the ImportListResourcesResult verb has been fixed in the 2020.2 release of the Orion platform.

Yes. Here is an example SWQL query adapted from this thread: Hourly Average bps- Need SWQL Help SELECT i.FullName, DATETRUNC('Hour', it.DateTime) AS Date, AVG(it.InAveragebps) AS InAveragebps, MIN(it.InMinbps) AS InMinbps, MAX(it.InMaxbps) AS InMaxbps FROM Orion.NPM.InterfaceTraffic it INNER JOIN Orion.NPM.Interfaces i ON…

@"Vinx" , are you using the following sample script as a template for what you are trying to do? https://github.com/solarwinds/OrionSDK/blob/master/Samples/PowerShell/ImportListResources.ps1

Please let me know if we have options to unmanage/remanage with .NET Powershell version5 without installing Orion SDK. Orion has a REST API for interacting with SWIS. You can use that endpoint from any platform that supports REST calls, including PowerShell. For details about the REST endpoint, see this:…

To get the account name, take a look at queries in the previously-mentioned post: Report on Muted and Unmanaged Entities The important parts are these: ... CASE WHEN ae.accountID IS NULL THEN 'Audit Log Not Found' ELSE ae.AccountID END AS [Account] ... JOIN ( SELECT ae.NetObjectID, ae.AccountID, ae.timeloggedutc FROM…

I have a correction to my earlier response. The discussion at Re: Adding node with DNS instead of IP indicates that an initial IP address should be provided even when setting DynamicIP to True. An updated example follows, which imports socket and calls socket.gethostbyname to get the current IP address of the node you want…

I agree that the problem is not in the code in your library. I think the key is here: System.IO.FileNotFoundException: Could not load file or assembly 'Castle.Windsor, Version=3.3.0.0, Culture=neutral, PublicKeyToken=407dd0808d44fbdc' or one of its dependencies. The system cannot find the file specified. That error message…

The introduction that you linked to is a great place to start for learning about interacting with the SolarWinds Orion SDK. There is more information here: https://github.com/solarwinds/OrionSDK https://github.com/solarwinds/OrionSDK/wiki However, it seems like you may also be interested in learning about the CnMaestro…

See Enabling SSL Certificate Verification for the SDK for details about this behavior. If you omit the verify parameter, the default behavior will be to skip SSL certificate verification, which is convenient since Orion uses a self-signed certificate that won't be trusted by default. The library is open source, so you can…

This issue is now marked as fixed with the UDT 3.4 release. CRUD operations are now supported for UDT ports (internal issue UDT-575).

I checked, and I'm afraid the issue is still unresolved.

You can add a WHERE clause that filters the results by the node name, ID, or some other property of your choice. An example that looks for two specific node names follows: SELECT n.NodeName, n.DetailsUrl AS NodeDetailsUrl, i.InterfaceName, i.DetailsUrl AS InterfaceDetailsUrl, i.InPercentUtil, i.OutPercentUtil FROM…

I created a GitHub issue to capture this here: https://github.com/solarwinds/OrionSDK/issues/204

The curl example is very helpful. It certainly looks like that should be working. I'm not sure why you would be finding that it isn't updating the custom property that you've specified there. The only next step that comes to mind is to use the SolarWinds Log Adjuster to really crank up the detail in the SWIS logs…

That table is documented in the wiki here: IPAM 4.5.x API · solarwinds/OrionSDK Wiki · GitHub The table contains these values: ValueName0Unknown1Used2Available4Reserved8Transient16Blocked

I tested with SWQL Studio on a 2019.4 installation, and the query runs fine. When I add that query in a Custom Query widget, I do see the error: I checked the SWIS log file at C:\ProgramData\SolarWinds\InformationService\v3.0\Orion.InformationService.log. I see this: 2019-12-04 14:16:13,393 [97] ERROR…

Orion.DiscoveredVolumes would be another place to check. It looks like a discovery process is involved in building the resource list.

FULL JOIN for non-passthrough queries is now supported (internal issue PLA-80), for Core 2018.3 and later.

To get more information about your query, you can run it with the WITH QUERYPLAN option (at the end of the query) in SWQL Studio. When you do that, you'll get an extra Query Plan tab next to the Results tab. That will have a bunch of XML including a <passThrough> element that contains a SQL (not SWQL) query similar to…

This log on the Orion server may have additional details: C:\ProgramData\SolarWinds\InformationService\v3.0\Orion.InformationService.log See this thread for additional discussion that may describe the same issue: REST API returning 403 Forbidden for Admin user

The IPAM team is working to fix this under internal issue IPAM-3384.

You may also be interested in inspecting alerts to identify what needs attention. You can find details about using the Orion SDK to interact with alerts here: Alerts · solarwinds/OrionSDK Wiki · GitHub

What does your SWQL query look like? When you run the query, do you find any error messages at the end of the log file at C:\ProgramData\SolarWinds\Logs\Orion\OrionWeb.log on the Orion server?

This issue is tracked at https://github.com/solarwinds/OrionSDK/issues/191 . Thanks for submitting that, kwimmer​!

A SWQL query like this would help you start taking a peek at which credentials are assigned to your nodes: SELECT TOP 1000 n.NodeID, -- From nodes n.IPAddress, n.Caption, s.NodeSettingID, -- From settings s.Description, s.SettingName, s.SettingValue, c.ID AS CredentialID, -- From credentials c.Name, c.Description AS…

The following documentation describes your options for working with certificates for the Orion server: https://documentation.solarwinds.com/en/Success_Center/orionplatform/Content/Core-Enabling-and-Requiring-Secure-Channels-with-SSL-sw1514.htm…

There is now an index page that allows you to select between the most recent two versions of the schema: SolarWinds Information Service v3.0 Schema Documentation Index Entity relationship information is also available again now.

I will see if I can arrange to have multiple versions of the schema documentation available, and I will investigate what happened with the entity relationships.

There is a casing problem with some of the files. If you capitalize the 'f' in "Netflow", you can see the updated documentation: http://solarwinds.github.io/OrionSDK/schema/Orion.NetFlow.cbQoSConfigurationDetails.html I'll see if I can get a fix in place for that.

This is a confirmed bug. It is tracked internally as issue DC-3254. It has been fixed in the candidate builds for the next release of Orion.