tdanner ✭✭✭✭✭

In PowerShell, it would look like this: $uri = "swis://tdanner-dev.swdev.local/Orion/Orion.Nodes/NodeID=1" Remove-SwisObject $swis $uri To find out the Uri for a node, just query for it: $uri = Get-SwisData $swis "SELECT TOP 1 Uri FROM Orion.Nodes WHERE [your criteria here]"

I can't give dates, but we are working on it.

Yes, Kerberos auth is still not supported for the SWIS REST endpoint.

I'm not sure where the old DNS entry is coming from. Maybe your reverse DNS records (PTR) are stale for some reason? Discovery should only be using credentials that are listed in the discovery profile. If there are no SNMP credentials in the discovery profile, then it shouldn't be doing SNMP at all. Are there any…

The work to fill in this support is tracked as NPM-5162, but I don't have a release target for you.

No problem. Same sample, translated to Python: https://github.com/solarwinds/orionsdk-python/blob/master/samples/ncm_execute_script.py

So something is going wrong with a temporary file generated by .NET's XmlSerializer class. What versions of PowerShell and the .NET framework are installed? Can you try the script on another machine and see if it has the same problem there?

If you have a plain text table and you want to send it as HTML, you need to wrap it in <pre> ... </pre> tags. Otherwise all of the whitespace will be reduced to a single space.

You have chosen... wisely.

Try specifying the domain as part of the credentials. Like this: curl -v -k -u yourdomain\\dqian -X POST ... (backslash doubled to escape it from the shell - needed on *nix but not windows)

Try WHERE (Nodes.Caption LIKE '%D49%')

If you post the inputs that are leading to this error message, I might be able to guide you.

The recommended way to create new reports is through the website GUI. What are you trying to do?

Looks like Michael hasn't created a "release" on codeplex. But the source code is there, so you should be able to just grab the files from https://powerorion.codeplex.com/SourceControl/latest

I haven't tested it, but I don't see any obvious errors. If it is working for you, cool.

The custom query resource should work with any query that works in SWQL Studio. Have you tried something really simple like "SELECT Caption FROM Orion.Nodes" to make sure something else isn't broken?

Yes, that's right. Actually, in your path (.\Inetpub\SolarWindsNPM\Orion\NetPerfMon\Resources\*******) the "*******" doesn't affect what type of view they go in. That's controlled by the "RequiredInterfaces" property in the code for the resource. The "*******" directory just controls what group they go in on the Add…

Ok, you have an error result instead of a Uri. Are you using the current version of swisclient.py? That should have throw an exception, not returned the error as if it were a valid result. Anyway, the key line from that big error message is "Error : In property EngineID. Reason : Invalid EngineID. Value : 1." That…

SWIS doesn't track max string length. You would have to work out the corresponding field in the SQL database (where applicable) and look at that schema to see the max length.

Unfortunately, Orion.APM.Component does not support the "update" (Set-SwisObject) operation. I have referred this thread to the SAM team to see if they can offer an alternative way to accomplish your goals.

The version of powershell wouldn't matter. What version of NPM are you using?

There have been some properties added to nodes and interfaces since 9.5. Maybe your query was using one of them? The exceptions should mention the name of the property if that is the issue.

In PowerShell the "Remove-SwisObject" cmdlet can be used to delete a node from Orion. You need to get the node's Uri first. You can use a query like this to do that: SELECT Uri FROM Orion.Nodes WHERE --your criteria here

Yes, that's still the address for the API. I was more asking about what specific features you use via the API.

Different production environments have different standards of what maturity they require, so that's a judgement you'll need to make for your own environment. I can tell you that there are a number of companies not just using the SDK in production but selling products to their customers that leverage it to automate NPM. I…

I did some digging and found that it does load the interfaces (to get their status) for each node when it needs to link to that node. But the whole point of using ajax for that tree is that it only needs to link to nodes when you expand a group. Unless you have your grouping set to "None", it should not need to display all…

You may be hitting the deadlock described here: http://blog.stephencleary.com/2012/07/dont-block-on-async-code.html The recommended cure is not to use ".Result". Instead, use "await" to get the result of the task.

Your use case makes perfect sense, but there is not a way to do this today.

A few weeks ago you posted about poor performance of this verb: Alert Suppression Question. Are these timeouts just a result of those performance issues? How many nodes are you suppressing in a batch?

Are you connecting to port 17778? The REST API is not part of the Orion website - it is hosted separately and on a separate TCP port.