tdanner ✭✭✭✭✭

The "RETURN XML AUTO" format is designed to work with queries that use navigation properties instead of explicit joins. If you want to use that output format, the equivalent query using navigation properties looks like this: SELECT B.NodeID, B.Caption, B.CustomProperties.Scripts, B.CustomProperties.GroupFROM Orion.Nodes…

The address for SWISv3 is https://$hostname:17778/SolarWinds/InformationService/v3/OrionBasic

Yes it is, among many other fixes.

Please see this thread: Automating node additions e2e: including Hardware Health Sensors

This problem should be fixed in the v3 wsdl. You should be able to access it at https://orion-server:17778/SolarWinds/InformationService/v3?wsdl with NPM 10.3 or later.

The Orion website makes HTTP requests back to itself for various purposes. The IP address and port used for these connections are set in \Inetpub\Solarwinds\Orion\Custom.config. Could you tell us a little bit more about your setup? Are you using Windows authentication? SSL?

I would try to get the discovery problem addressed through SolarWinds support. Why is it not processing all of the agent nodes?

Invoke-SwisVerb takes four parameters: 1. The SWIS connection object. 2. The name of the entity type. 3. The name of the verb. 4. The list of parameters for the verb itself. You need to take those parameters and put them in a powershell list. This is done by wrapping them in @( ... ). So the full command line should look…

There's a known problem in 8.5 with passwords that contain special characters like # ? and &. Logging in with such a password produces an error like you are seeing. Could that explain it?

That's strange. What else can you say about this? Like how often does it happen, what method are you using to connect, etc.

Here's what's going on: the Custom Query resource is seeing adding an ORDER BY clause to your query to support sorting and paging. But it is doing it in a dumb way: it's adding "ORDER BY 'Notes'". But you are not allowed to order by a constant when there is a UNION in the query. To work around this problem, add your own…

The Orion alerting system does not provide a way to execute a powershell script on a remote system, but PowerShell has a set of remote execution features you could use. Start here: Running Remote Commands | Microsoft Docs

Invoke-SwisVerb needs an array of argument values. If the verb in question takes only one argument (like RemoveDependencies does), then you need to supply an array of one argument. The argument type needs to match (or at least be "close enough" for SWIS to convert it to) the verbs parameter type, which is an array of ints…

The connection profiles are not available through the query interface. However you can fetch one of them using the Cirrus.Nodes.GetConnectionProfile verb (expects one argument, the ID of the profile to get) or all of them using the Cirrus.Nodes.GetAllConnectionProfiles verb (expects zero arguments).

Also new in SDK version 1.3: cmdlets for Windows PowerShell. This is the easiest way to script Orion. More detailed documentation is available in the package, but here's a sample: Add-PSSnapin SwisSnapin $swis = Connect-Swis Get-SwisData $swis 'SELECT NodeID, Caption FROM Orion.Nodes' Get-SwisData $swis 'SELECT NodeID,…

This sounds like a problem we've started seeing where some browser reject the cookie our website sets. Customers who have had this problem have been able to work around it by making this edit: Edit C:\Inetpub\Solarwinds\Orion\Login.aspx.cs. Towards the end of the file, find this line:…

I'm not sure exactly what you are looking for. How would you do the same task through the UI?

Can you make a simple script for adding a WMI node with volumes that demonstrates the problem?

Did you intentionally scramble that Authorization header before posting this message? Because it is not valid base64 as it is.

Accounts are created and updated using verbs. See http://solarwinds.github.io/OrionSDK/schema/Orion.Accounts.html (at the bottom of the page) for a list. Let me know if you want examples.

Did you stop the NetPerfMonService before making the change in the database? What's the sysobjectid for that device?

This sounds like buggy behavior. I recommend you open a ticket with SolarWinds Support.

Connect-Swis connects to SWISv3 by default. There is no "-v3" switch. If you need to connect to SWISv2 (for example, to work with NCM versions earlier than 7.3), you can add the "-v2" switch.

We don't currently have a REPLACE-equivalent function in SWQL, and unfortunately I don't see a way to accomplish this without one.

Some resources may resolve those ${macros} in their query filters. Unfortunately I don't have a list of which ones would do that. The Worldwide Map resource does not.

Start by reading PowerShell · solarwinds/OrionSDK Wiki · GitHub and Alerts · solarwinds/OrionSDK Wiki · GitHub​. The commands you need are Connect-Swis (to get a SwisConnection object) and Get-SwisData (to run a query for alert info).

Unfortunately there is no short API call that can do this. But you can build a script that will do that the job and call that from chef. I recommend using the Discovery API for this. Docs: Discovery · solarwinds/OrionSDK Wiki · GitHub PowerShell sample:…

Documentation is here: Home · solarwinds/OrionSDK Wiki · GitHub SWQL Studio (available for download here: Latest release) is the best way to browse the schema.

It should have been registered by the installer, but apparently that didn't happen. You can do it manually as well: C:\Windows\Microsoft.NET\Framework\v2.0.50727\InstallUtil.exe "C:\Program Files (x86)\SolarWinds\Orion SDK\SWQL Studio\SwisPowerShell.dll" C:\Windows\Microsoft.NET\Framework64\v2.0.50727\InstallUtil.exe…

You are adding nodes for ICMP (ping) polling only. If you want more detailed monitoring (CPU, memory, interface utilization, etc.), you need to add the nodes as SNMP and provide appropriate monitoring credentials.