tdanner ✭✭✭✭✭

To deal with illegal filename characters, you could change this part: (Join-Path -Path $exportPath -ChildPath $filename) to this: (Join-Path -Path $exportPath -ChildPath ($filename -replace "[^A-Za-z0-9 _]","_"))

What directory did you put it in?

Then it should be listed in the "Miscellaneous - Miscellaneous Resources" category.

pbhcpa - Did you hit "Customize this view" on your Node Details page and then add the Poll Now resource? It doesn't get added to your view automatically.

pbhcpa - check the permissions on the file. Compare them with other files in the same directory. If IIS can't read the file, it won't show up in Add Resources.

You don't have to be an administrator, but you do need the "Node Management" right.

Those little icons (I assume you mean the strip at the top right of Node Details) are in \Inetpub\SolarWinds\Orion\NetPerfMon\Controls\IntegrationIcons.ascx. It should be possible for someone familiar with ASP.NET to put the code from this Poll Now resource into that strip. You would want to omit the ResourceWrapper layer.

The zip file contains one file: PollNowResource.ascx. Take this ascx file and drop it in \inetpub\solarwinds\Orion\NetPerfMon\Resources\NodeDetails. Go to the website and customize your node details view to add the new resource.

You could try something like this (not tested): import socket results = swis.query('SELECT TOP 1 NodeID FROM Orion.Nodes WHERE DNS=@dns', dns=socket.getfqdn())

What do you mean by "the current node"?

I don't think you can use wildcards, but I think you can you range queries like > or <

SAM is our Server and Application Monitor product. It provides the Orion.APM.Component, Orion.APM.CurrentStatistics, and Orion.APM.Application entities referenced in that query (among many other features).

There are a number of variations on the query in this thread, and many of them rely on the SAM product. Do you have SAM installed? If so, what version? Also, please post the query you are using.

Wrong port. The API is on port 17778.

There's more information on the github wiki (Home · solarwinds/OrionSDK Wiki · GitHub) and sean.martinez‌ posted some great info on thwack: Orion SWQL, Thwack! Now I got it.

Container filters lack the "not" operator. The the number of possible "DeviceFunction" prefixes is managable, you can exclude one prefix by just OR-ing together all of the others. Like this: filter:/Orion.Nodes[Contains(CustomProperties.DeviceFunction,'Lync') AND (StartsWith(CustomProperties.DeviceFunction,'AAB') OR…

You can update the status of a node in Orion with a web api call. You will need to provide the URI of the node to update (explained here) and one of the status values (numeric) that Orion uses (documented here). See GitHub for a general intro to the API.

Could you elaborate a bit more on what you are trying to do and what tools you want to use to do it?

As it happens, I do have that sample. The plan is to add it to the next SDK release, but I can post it here.

What results are you seeing? Error from the server? Server returns false? Something else?

Yes, you can do this in bulk, but you need a different call to do it. Like this: $swis = Connect-Swis -Hostname yourserver -Trusted $uris = Get-SwisData $swis "SELECT Uri FROM Orion.Nodes WHERE blah blah blah" $start = [DateTime]::UtcNow $end = $start.AddHours(1) $uris | Set-SwisObject $swis -Properties…

If you have a working SWISv2 client, the URL should be the only thing you have to change to get a working SWISv3 client. Could you give more detail about what you are seeing returned from v3?

The "right" way to edit the location depends on the device type. For Windows machines, use the Services services snapin (or the Serivces node in Computer Management) -> properties of the SNMP Service -> Agent tab -> Location field. For Cisco (IOS) devices, set "snmp-server location XXX" in configure mode. Other devices…

You can just always call the verb on the primary polling engine. It will take care of directing the actual discovery operation (SNMP queries) to the polling engine your node is assigned to.

Rather than fight with WSDL issues (it didn't work for me when I tried it either, and the error message "Selection must be WSDL" is unhelpful in the extreme"), I recommend you switch to the JSON endpoint. All of the same operations are available and the formats is described in the same document. We don't have a complete,…

You could use a query like this to confirm that the credential is of the correct type: SELECT ID, Name, CredentialType, CredentialOwner FROM Orion.Credential WHERE ID=23 Also, you can use the magic value -3 as the credentialId to use the node's assigned monitoring credential for the service restart operation.

No, FSM does not have a public API at this time.

From your PowerShell script in the other thread, you can see the sequence of Invoke operations needed to execute a CLI operation through NCM. And from your Python code in another thread, you are able to run basic SWIS operations over the REST endpoint from Python. Are you having trouble making the invoke calls from Python?…

Yes, this was inadvertently broken in NPM 12.3. It's fixed in NPM 12.4, which is currently in the release candidate stage.

You can import a report with the CreateReport verb on the Orion.Report entity. It expects these parameters: * name * description * limitationCategory * category * title * subtitle * definition - the report defintion in XML form * isFavorite - not sure why this is declared as a string, since it must be "true" or "false" *…