tdanner ✭✭✭✭✭

SWIS uses different syntax for some functions than SQL. The various DATEDIFF SQL functions are represented as DAYDIFF, HOURDIFF, MINUTEDIFF, SECONDDIFF, etc., in SWQL. Instead of CURRENT_TIMESTAMP, you have GETDATE().

The LogAdjuster program on the Orion server can help you get more details into your logs. I usually set it to DEBUG. If you can share the C# code you are using, I might be able to spot the issue.

What the "List Resources" process actually does is somewhat complicated and, unfortunately, not directly exposed through anything you could call. We are testing a possible solution that might give you what you need. I should be able to let you know soon if it works out or not.

To configure views by device type, click Admin, then "Views by Device Type" in the Views box (top right).

Sorry for the late reply - I lost track of this thread. That query works for me if I add the "SELECT" at the beginning, though I know from your other thread (SWQL Complex query ) that you are on an older version of the platform - you might be hitting some bug we fixed years ago. To get more details about the error, you can…

The AlertDefinitions table relates to the "Advanced Alerts" system. This is the system that was replaced by the "alerting v2" system that has the web-based editor. In 11.5 you could use either system. I agree that those XML blobs are not human friendly. The are produced by serializing the model objects using…

Starting a discovery job using an existing discovery profile uses a different verb than starting a discovery job creating a new profile. Fortunately it is much simpler: $discoveryProfileID = 123 # get the discovery profile id from somewhere, such as by querying Orion.DiscoveryProfiles to find the one you created in the UI…

Almost there. Orion.AlertConfigurations.Import needs the xml dump of the alert as a string. The return value from Orion.AlertConfigurations.Export is the alert xml as a string, but it is wrapped in an XML element. As you discovered the ".InnerText" of this object is the string we need. # On system A $ExportedAlert =…

It seems that the PropertyBag deserializer doesn't like whitespace between the xml tags. When I fed in your request, I got the exact same error. I was able to work around the problem with a request like this: <soapenv:Envelope xmlns:soapenv="">schemas.xmlsoap.org/.../"…

The unmanage API requires the NodeID. If what you have is the DNS name, you can look up the NodeID using a simple query: SELECT NodeID FROM Orion.Nodes WHERE DNS='my.dns.name' As a curl command, it would look like this: curl -k -u username:password…

See this page for a more detailed discussion of SWIS Uris: Uris · solarwinds/OrionSDK Wiki · GitHub . Your Uri is missing the "endpoint" segment, which would normally be "/Orion/". Change the first line to this: $uri = "swis://ServerFQDN/Orion/Orion.Nodes/NodeID=$($nodeId)/CustomProperties" In general the "safest" way to…

It's not in the current release candidate, so it won't be "weeks". Beyond that I'm not at liberty to talk timelines.

To remove an interface entirely (permanently), get its Uri and call swis.delete() on that. SwisClient.py shows an example of how to query for the Uri of a node; doing it for an interface is similar.

Verb arguments are provided as an array, not an object with named properties. Also, AppendNote expects a collection of alert object id values, not a single value. In PowerShell, you can produce the required POST body like this: @( @( 12 ), 'newnote' ) | ConvertTo-Json

In SWQL Studio, are you using the "Orion (v3)" server type?

At this point we have full support for custom properties/columns for Nodes, Volumes, Interfaces (NPM), and Applications (SAM), but not whole custom tables. I'm sorry, but you're on your own for that.

There's no setting to turn that off. The only solution I can think of would be some sort of automated query to delete those events from the database frequently.

That page uses C# notation to describe the verbs, but converting to a JSON payload is straightforward. If you have verb "VerbName" on entity "Orion.EntityName", then the URL to call it is /SolarWinds/InformationService/v3/Json/Invoke/Orion.EntityName/VerbName. Pass the argument values as a JSON array. So to deploy an agent…

User jfoley posted some PHP code for running a query in this thread: Re: Orion SDK Information ini_set('display_errors', 'On'); error_reporting(E_ALL); $endpoint = "https://localhost:17778/SolarWinds/InformationService/v3/Json/Query"; $post_data = array( 'query' => "SELECT TOP 1 DisplayName, DetailsUrl FROM Orion.Nodes" );…

You are welcome to try it, but I can't really endorse that.

That verb causes NPM to scan the device (using SNMP) for all interfaces. On a device with many physical or virtual interfaces, it is not outside the realm of possibility that it could take 28 seconds to do this. But that verb does not cause any changes to the NPM configuration. You have to take the output, remove elements…

No, there is no equivalent for volumes. Easiest way to see what's in the DiscoveredLiteInterface structure is to just dump it to the console. Or run it in a debugger and check it out there (if you are using PowerShell, the PowerShell ISE debugger works fine).

SWIS only supports RIGHT JOIN for queries that it can translate entirely to a single SQL Server query. One of the entities in your query (Orion.AlertObjects) is handled by code in SWIS, so it can't send the whole query to SQL Server. SWIS's in-memory query processor can't handle the RIGHT JOIN. In general, queries that use…

Is this the IP address of the SQL Server or the Orion server? It should be the Orion server.

What are you trying to accomplish? You have created a "system" account, which is not really intended for logging into the website. It's just intended for API use. System accounts are not blocked from logging into the website, but they are not provisioned with all of the settings needed to make the website work properly. If…

Hmm, this works when I try it. What version of NPM are you using?

What version of NPM are you using?

Here's a thread that describes how to do conditional formatting of data using the Custom Table resource. Note that the Custom Table resource is different than the Custom Query resource and does not recognize the _IconFor_XX and _LinkFor_XX conventions - it has its own way to handle links. Text colour to display alerts…

You bet. SWIS only has six basic operations: Query, Invoke, Create, Read, Update, Delete. All of the interfaces (REST, SOAP, and PowerShell) support all of these operations. Anything you can do with one, you can do with the others. Only the syntax will be different.

Invoke Request POST https://localhost:17778/SolarWinds/InformationService/v3/Json/Invoke/Metadata.Entity/GetAliases HTTP/1.1Authorization: Basic YWRtaW46User-Agent: curl/7.20.0 (i386-pc-win32) libcurl/7.20.0 OpenSSL/0.9.8l zlib/1.2.3Host: localhost:17778Accept: */*Content-Type: application/jsonContent-Length: 39["SELECT…