Quantcast
Channel: THWACK: Message List
Viewing all articles
Browse latest Browse all 20396

Re: Re: How do we programmatically discover the non-interface properties [in Orion] and enable them

$
0
0

Wow, do I have to add each one of those in a separate call?

 

Also, can you show me what that looks like as a REST call? (What the json body/data needs to look like.)

Actually, I went back to the PDF docs and I see body data that looks like this: {"PollerType":"hi from curl 2", "NetObject":"N:123", "NetObjectType":"N", "NetObjectID":123}  Although, "hi from curl 2" doesn't make much sense if I'm trying to specify one of the pollers in the list. Can I assume that "$poller" in your example somehow represents, for instance, "N.Routing.SNMP.Ipv4CidrRoutingTable" ?  And if so, is that the string that goes in there, or... ?

 

Oh, also, in the documentation it appears that if my poller addition is successful, I get back the swis:// uri of the poller along with it's ID number. Is that correct?  And if my call fails, what should I be looking for as a return value?

 

 

Thanks again,

Scott Fraley


Viewing all articles
Browse latest Browse all 20396

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>