tdanner ✭✭✭✭✭

Here's the REST equivalent of some of the PowerShell operations in the CRUD.AddNode.ps1 sample: PowerShell RESTNew-SwisObject $swis -EntityType "Orion.Nodes" -Properties $nodeProps return value: new object's Uri POST https://server:17778/SolarWinds/InformationService/v3/Json/Create/Orion.Nodes body: node properties as a…

Custom properties - yes Select which items to monitor - limited flexibility here. This shows how to selectively add interfaces OrionSDK/NPM.DiscoverAndAddInterfacesOnNode.ps1 at master · solarwinds/OrionSDK · GitHub, but there's no granular control for other areas. Assign application templates - yes. See…

I don't know of any workaround other than applying ToString to the affected fields. You could call up support and tell them that CORE-8683 is causing problems for you and that you need a hotfix for 12.1. No promises, but referencing a bug by number should help.

No, I don't think you can do this with the SolarWinds SFTP server. This is really built around the use case of transferring network device configurations and firmware images. For general purpose file transfers, you might want to look at our Serv-U product.

This API does not provide a way to set the description of a discovery profile. You can add arbitrary extra fields to the object you send to StartDiscovery, but they will just be ignored by the json parser.

And here's the query: select distinct CASE WHEN CacheResults.DiffFlags = 1 THEN 'changed' WHEN CacheResults.DiffFlags = 0 THEN 'unChanged' ELSE 'unknown' END as NCMNodeStatus, NCMNodeProperties.NodeID, Nodes.NodeID as CoreNodeID, Nodes.VendorIcon, Nodes.Caption, Nodes.IPAddress, CacheResults.DiffFlags, Nodes.DetailsUrl,…

What do you mean "don't like the join"? Is there an error message? Joining to Orion.ContainerMembers could work, but that will only get you the innermost group ("Campb") in your picture. To work up to higher groups, you will need to run a separate query for each level out you need to go. And remember that an entity can be…

Argh! That's what I get for posting a query without testing it. Typo - it should be Orion.SEUM.Recordings. Like this: SELECT R.RecordingId, R.Name AS RecordingName, R.Transactions.AgentId, R.Transactions.Agent.Name AS AgentName FROM Orion.SEUM.Recordings R WHERE R.Transactions.AgentId IN (1, 2)

I'm afraid I don't understand your question. Is there a resource that you expected to recognize ${NodeID} that would not?

The historical statistics entities have a Weight property that can be used to properly combine samples at different rollup levels. The Weight property reflects the number of seconds that sample represents. So 3600 for hourly, 86400 for daily, and some smaller number for detail depending on your polling intervals. You can…

You are right - we can do better. I've changed 8.5.1 to use set the Custom Bandwidth option if either the InBandwidth or OutBandwidth differs from the InterfaceSpeed, otherwise the Custom Bandwidth will be off and In/OutBandwidth will track what SNMP reports. I think this will cover the case you brought up with asymmetric…

That's true, but with the right script that can be a very quick operation - write a script that checks whether all of the prod/dev subgroups that are supposed to exist do or not and creates any that are missing. You could even schedule that script to run regularly and not have to think about it any more.

The problem is that the group availability is computed based on the current members of the group and then stored in the history table. You can't come back later and retroactively subset the group - it has already been summarized. We could also just ignore the groups and compute node availability based on custom properties.…

Do you have .NET 4.5 installed?

I'm afraid not. Sorry about that.

You are getting result set multiplication because of how the ON clause in your join to Orion.NodesCustomProperties is written: right join orion.nodescustomproperties cp on o.networknode=n.nodeid Notice how the ON expression does not mention "cp"? This means that every row in Orion.NodesCustomProperties "matches" every row…

This property was added in Orion Platform 2018.4/NPM 12.4.

Some of the API functions have been added to micheal100​'s PowerOrion module. These are much more admin-friendly and include at least some basic documentation that is accessible to PowerShell's "Get-Help". OrionSDK/Samples/PowerShell/PowerOrion at master · solarwinds/OrionSDK · GitHub

This code will give you the date and time of the last login: <%=Profile.LastLogin %>

This was fixed in Orion Platform 2018.4/NPM 12.4. You can now set PreferredPollingMethod when you call CreateCorePluginConfiguration. It should be the last XML element in <CorePluginConfigurationContext>.

After checking the code, it looks like the missing property is DNS.

Back up the production SQL database. Restore this backup on the lab SQL server. Run the Orion Configuration Wizard on the lab instance to connect it to this new lab database copy. Then you will see this data when you query SWQL.

That installer includes only the web console and does not include the poller or other Windows GUI parts of Orion. Note: I don't recommend using any 8.5 build other than RTM.

Is that the whole stack trace? There should be more to it than that.

No response from them yet. Sorry about that. I will poke them. Until they respond, I can at least tell you that Orion.NetFlow.ConversationsTop expects three parameters: Filter, Limit, and TopKey. Try removing the Tx and Rx parameters from your query and see if it starts working.

Direct database insert might work, but we don't have instructions for it and it isn't something we can support. Unfortunately, I don't have another workaround to give you.

You can call the REST endpoint from PowerShell, but you need a few changes. The URL is https, not http, and the SWIS URI part should be included in the URL, not the request body. Also, since the certificated used by Orion on port 17778 is self-signed, you will get a certificate error from Invoke-WebRequest. You can avoid…

What problem are you seeing with the POST request from Java? Can you post the code and the response you get?

Ok, the first URL (on port 17778) looks correct. Visiting it in a browser won't do anything for you - it has no page to show. Did you fix the payload format to be JSON?

Looks like I missed this question in December. Sorry about that, Richard! And thanks Kevin for reviving it. The SWIS query interface is strictly readonly. You can't update this way. However, you can set custom property values through an update call. Make a POST request to…