tdanner ✭✭✭✭✭

No, there is not a method to delete discovery profiles. However, you may be able to avoid needing to do the cleanup later using this method. From https://github.com/solarwinds/OrionSDK/wiki/Discovery: Set the IsHidden option to true to cause the discovery profile to be removed after the discovery completes. Leave it false…

The second parameter for AddInterfacesOnNode is an array of interface objects. You are only adding one interface, but it still needs to be an array. Wrap it in [brackets] and see if that fixes it.

If you know the OID you want to monitor (for example, by copying it from the oidview site), you can use with with UnDP. Just paste it into the OID field. You don't have to wait for us to add the latest version of that mib.

Since this is running on the Orion server connecting locally, you can use certificate authentication. Try "Connect-Swis -Certificate".

I tried your script out and it worked fine on my system. The next troubleshooting step would be to look in the Information Service v3 logs and see if there are any more details. That file is: C:\ProgramData\SolarWinds\InformationService\v3.0\Orion.InformationService.log Please run the script again, then check that file for…

I can reproduce this problem as well when I use Visual Studio to generate a client. Apparently there is something Visual Studio doesn't quite like in our WSDL. I recommend you just avoid the Read operation and use QueryXml (or the instead).

We don't have an API specifically for getting the data from a report. However, if you can get a SWQL query that corresponds to the report, you can use the query API to get the data for manipulation.

Here's the scenario behind that bug: * You have Integrated Windows Authentication set in IIS * You have two Windows users - call them Domain\A and Domain\B. * In Orion, you have two accounts defined: Domain\A and DirectLink. * A and B receive an email with a link to an Orion report or something. * A clicks the link, is…

I can't see enough of your code in PowerShell or Python to say what's going on. Could you copy and paste it into a message in this thread? (You can xxxx out passwords, of course.) Also include the full text of any errors you get.

"SELECT Caption FROM Nodes" should be "SELECT Caption FROM Orion.Nodes" - that will probably work from the website. When you use the "Orion v3 AD" server type in SWQL Studio, you are connecting using the current Windows logon token. If the account you are logged into Windows with doesn't have access to Orion, then this…

At this time SAM only supports using the SDK to apply existing Application Templates to nodes, not creating new components. I'll let the product manager know about your request.

The Orion.AlertHistory SWIS entity does exist. Are you connected to SWISv2? This entity is only in SWISv3.

I think we were able to answer this question for you in another thread. Are these any other missing pieces for you?

The custom chart resource only supports time series data.

Something went wrong when the configuration wizard was supposed to load the website configuration into your database. Probably best to open a support ticket.

The problem is that the API to add volumes individually requires you to know how those volumes are identified in WMI. I suggest looking at the discovery API to add nodes instead. It is complex, but it will at least find the volumes for you. https://github.com/solarwinds/OrionSDK/wiki/Discovery…

Set the "Server Type" field in the login dialog to "Orion (v3)". Like this:

Historical response time values are in Orion.ResponseTime.

I'm guessing you are looking for node count by vendor. If that's the case, a query like this will work: SELECT Vendor, COUNT(1) AS QuantityFROM Orion.NodesGROUP BY Vendor Pro tip: these kinds of questions will be answered more quickly if posted in the Orion SDK forum.

No, there is no master list of pollers in the database - just in code. Leon, the Polling Engines listed in the Engines table are sometimes referred to as "pollers", but these are not the same thing jrchapman is asking about.

Remove "VolumeID" from your payload. Also note that to take this approach to adding volumes you will need to ensure you are populating creating the appropriate Orion.Pollers instances. I recommend you select an equivalent volume that was added via Discovery or List Resources and look to see what Orion.Pollers has for that…

Are you looking for historical data such as you would use to make a chart? If so, you are looking at the right entities. You can get last 24 hour CPU and Memory utilization with a query like this: SELECT CPULoad.Node.Caption, NodeID, DateTime, AvgLoad, TotalMemory, AvgMemoryUsed, AvgPercentMemoryUsedFROM Orion.CPULoadWHERE…

I referred your question to the IPAM team. They were not able to reproduce the problem, which tells us that your approach seems fine but that there must be something specific about your environment that is causing the error. They sent some follow up questions to track that down: * How was the subnet added? * Is this subnet…

Nope, you can only select one interface to represent a link. It's on our radar to fix this - you are not the first person to notice this limitation.

Setting custom property values on nodes in Orion is simple with SWIS. I'll let the community chime in with any similar experiences.

Instead of just "Vol_Owner" in the SELECT clause, put "Volumes.CustomProperties.Vol_Owner".

This should be pretty straightforward. # Open a connection to SWIS $swis = Connect-Swis -Hostname myorionserver.mydomain -Username mickeymouse -Password minnie # Get a list of Uris for the interfaces you want to change $uris = Get-SwisData $swis "SELECT Uri FROM Orion.NPM.Interfaces WHERE my-filter-expression" # Set the…

Please post the script. The usual cause of this is that the script is not providing a value for some properties that the website is expecting to be non-NULL. A future release of NPM improves this situation - SWIS will automatically fill in default values for properties when you are adding nodes through the API instead of…

This is not something the SDK supports today. Your best bet is to query Orion.AlertStatus every so often and track changes.

Unfortunately the API does not currently provide a way to ignore interfaces for discovery. This database method is the best available workaround for that limitation.