tdanner ✭✭✭✭✭

Adding a node is done using a "create" operation, not "invoke". The C# sample does not have a wrapper method for create, but it should be straightforward to make one given the request format, which is shown here: https://github.com/solarwinds/OrionSDK/wiki/REST#create-request.

In general, you can query for the properties of any entity type by querying Metadata.Property, like this: SELECT NameFROM Metadata.PropertyWHERE EntityName='Orion.NodesCustomProperties' However, this will include navigation properties and inherited properties like Uri and InstanceType that you probably aren't interested…

What version of NPM are you using? And are all your devices using SNMPv3?

No problem. In the chart url, there's a parameter that looks like this: CustomPollerID=9d86ec5b-e953-4ac9-99d4-9b810f75e76c Change it to this: CustomPollerID=${PollerID} For this to work, you need to add the PollerID field to your report. I found it under "Custom Pollers (Current Status) > Custom Node Pollers > PollerID".…

Confirmed. This feature request is tracked internally as SAM-7012.

Like mrxinu​ said, as long as you keep the name safely unique, custom tables in the Orion database shouldn't be a problem.

That helps. So in this scenario, there are three relevant servers: 1. The Orion web server. ASP.NET, IIS. Typically on port 80. 2. The Information Service. Running on the same server as #1, but not in IIS. It's hosted by SolarWinds.InformationService.ServiceV3.exe and the REST API is on port 17778. This API is implemented…

Unfortunately there is no SWIS API equivalent for that "rediscover agents" checkbox. I have added a link to this thread to the internal case (DC-1537) to serve as a vote and a reminder to reply in this thread when this gets implemented and released.

Try using the XML parsing approach that gstewart used in his post on 2013-06-14 in this thread.

We have a few samples for how to do various tasks in the Samples\PowerShell directory. When you want to do something with the API, I recommend you start by seeing if there is a PowerShell sample for that task. If you find one, you can do the same operations in Perl. You may have to do a bit more XML-wrangling in Perl than…

No, this issue is not addressed in hotfix 1. Currently it is scheduled for the next normal Orion release.

Thanks. I reported these two issues to the IPAM dev team.

Where are you using this query? Some places that accept a custom query have ways to make links and some don't.

One way to achieve this would be to use Views By Device type to give a different node details view for your BlueCoat devices. On the BlueCoat Node Details view, add a Custom HTML resource, with contents like this: <a href="https://${IP_Address}:8082">Browse to ${NodeName}</a>

Nothing yet.

Are you using the Preview button on the Customize View page? When you are editing a "details" type view that requires a net object (like Node Details, Interface Details, Application Details for APM, etc.), the Preview button basically just chooses a device at random so it can show you what your layout looks like. If you…

4.6: https://github.com/solarwinds/OrionSDK/wiki/IPAM-4.6-API#crud-operations-for-ipamipnodeattr

I'm glad its working for you. Be careful though - this web.config edit will be overwritten on the next upgrade.

What product/version are you using?

Let's discuss this privately.

Think of the equation for a line. It has a slope and an offset. The offset is "A" and the slope is "B". That's it.

It only updates the forecast daily. If the volume is filling up much faster than the forecast, you would be relying on the normal (non-forecast) volume usage alert to save you.

I would recommend sticking with the discovery API - it will take care of a bunch of details that require more node-type-specific code when you use the New-SwisObject method. The hardware health stuff was added correctly when we tried it. We'll follow up with some troubleshooting steps. No, unfortunately we don't have a…

You would do this in the Orion website. The node tree and maps are not directly related.

No, that's not supposed to happen.

Based on the error you posted at the begining of the thread, I can see that we're not finding the BusinessLayerPort column of the Engines table in the database. This is a new column that was added in 9.0. There were other database changes in 9.0, so just creating this column won't be sufficient to get everything working. I…

Those times need to be specified in UTC. Depending on when you ran that script, you may have specified a 5-minute window several hours in the past.

That is correct - we don't offer the API over non-SSL connections at this time. Could I ask why you are looking for plain HTTP access?

You can't pass the @nodeID array directly, but you can expand it into the query. Like this: SELECT Caption, Status, ResponseTime, PercentLoss FROM Orion.Nodes WHERE NodeID IN (1, 2, 3, 4)

There's nothing specific you need to do to Orion unless you want to run HTTPS on something other than the default port of 443. Just go through the same setup as for any other IIS website and you should be good to go.