tdanner ✭✭✭✭✭

The JSON serializer is much more forgiving on these sorts of things. I'm thinking about adding an option to SwisPowerShell to use json instead. XML would still be the default for compatibility with existing scripts.

Please post details about what you have tried and what you are seeing here. Are you working with the original poster? This thread was opened over a year and a half ago - it is not obvious to me that your issue is the same as his.

Please also check the SWIS log. C:\ProgramData\SolarWinds\InformationService\v3.0\Orion.InformationService.log

No, unfortunately we don't have an API for changing the polling method short of deleting the node and readding it. And as you pointed out, that means starting over with all of the other configuration that has been done with the node. And I'll save you the suspense - the upcoming SolarWinds Lab episode does not cover this.

Ok, that helps. What was the original SWQL query? And what version of NTA are you using?

Are you running this on the Orion server? Because as written this is going to try to connect to localhost. Also, it looks like you are using an older version of the SDK. The last few versions (available at Releases · solarwinds/OrionSDK · GitHub) have not included the "Orion SDK.pdf" file because the documentation has…

The bug is CORE-10524. Support can check on the status using that number. It's not fixed in the Orion Platform 2018.2 (NPM 12.3) release candidate, but it should be in the next release. I can't promise anything though.

No, there's no API for this yet.

When an alert is triggered, it only looks at the reset condition. If I understand what you want to do, I think you can just use the "Reset when trigger conditions are no longer true" radio button on the Reset Condition tab.

The second parameter for AddInterfacesOnNode is an array of interface objects. You are sending a bare interface object. SWIS is behaving like it parsed an empty array of interface objects. Try keeping the original return value from DiscoverInterfacesOnNode and just removing the DiscoveredLiteInterface elements that you…

Have you looked at the XML that comes back? You should be able to write your XPath easily then. Note that you can change "RETURN XML AUTO" to "RETURN XML RAW" in the query to get a different (simpler) XML serialization back.

For the roadmap question, see What are we working on for IPAM (Updated on October 20, 2016) . Please contact ding​ (IPAM Product Manager) if you have more questions in that area. There is no workaround for the current version.

Strange - so you had the registry keys for AppMon but none of the files? Are you able to upgrade to 9.1 now?

It looks like you are discussing this issue with derhally‌ in another thread: SWIS v3 stop working suddenly

This behavior is part of SWISv3, which updates with the product, not the SDK, which is mostly independent of the product version. This error will be the same with any SDK version. In NPM 11.5, we improved error reporting from SWIS. For a large class of errors, including this one, you will now get a decent error message…

The error you are seeing "Object reference not set to an instance of an object" is coming from the server. It looks like the sample client is trying to acknowledge an alert that does not exist.

Yes, you can raise alerts on "external" nodes. That might be the best way for tkercher​ to make this work: create a placeholder external node for each radio channel and set the name of that node to that channel's six character identifier.

If I understand correctly, you want to look up a NodeID by matching the last 6 characters of a trap tag with the node's caption. Is that right? Here's a simple query that will do that: SELECT N.NodeID, N.Caption, N.Status FROM Traps T LEFT JOIN Nodes N ON RIGHT(T.Tag, 6) = N.Caption Working that into your trigger condition…

I would have expected it to work as an IPAM admin. Let me check with the IPAM dev team and see if we can figure this out.

That makes a lot of sense. I don't believe it is possible today, but I have sent this as a feature request to the product manager for IPAM.

That's my mistake. This is the syntax for macros in the new web-based alerting system (currently at the release candidate stage). Let me correct my earlier post to reflect the macro syntax for the old Advanced Alerting engine that kbailey@tivo.com is using.

<a href='' target="_blank"> <img src="/Orion/images/ToolsetIntegration/Small.SSH.gif" alt="Open an SSH session to " title="Open an SSH session to " /> </a> Looks like part of this is missing. Don't you need to reference the hostname or IP address somehow?

It is probably not worth the trouble to implement this kind of filtering in SWQL. Since this is happening in the context of a larger script, I would just use SWQL to fetch all or a chunk of the subnet (if you use mostly /24s this will work well; if /16s not so much) and apply your business logic to select the appropriate…

DayDiff expects two parameters and returns the number of days between them. Like this: WHERE DayDiff(timestamp, GetUtcDate()) < 7 -- Matches all timestamps less than one week old

Ok, for Checkbox method, pass null for parameter 2 and send the ContainerID values as an array in parameter 3 (even if there is only one ContainerID, put it in an array). Like this: POST https://servername:17778/SolarWinds/InformationService/v3/Json/Invoke/Orion.Limitations/CreateLimitation [18,null,[1,2,3],null,"guest"]

The API consists of a pair of verbs: Orion.NPM.Interfaces.DiscoverInterfacesOnNode and Orion.NPM.Interfaces.AddInterfacesOnNode. There's a sample script here: https://github.com/solarwinds/OrionSDK/blob/master/Samples/PowerShell/NPM.DiscoverAndAddInterfacesOnNode.ps1 .

I don't have a date for you, but that's a feature request that is important to me.

_IconFor_ and _LinkFor_ are the only magic column names at this time. "High errors and discards today" has extra code to handle that highlighting. It's not available generically.

By default, views in Orion refresh every 5 minutes. You will see the current node status at that time.

Are you on NPM 11.5.0? That version has a known bug with custom properties and nodes added via the SDK. 11.5.2 fixes it.