tdanner ✭✭✭✭✭

This information is not currently available through the SDK. I have opened a feature request to get it added. The internal number is 53940.

This higher-level API is the idea behind micheal100‌'s PowerOrion PowerShell module. You can get it at OrionSDK/Samples/PowerShell/PowerOrion at master · solarwinds/OrionSDK · GitHub. It's not comprehensive by any means, but what it does have is in the spirit you describe. The reason you are getting errors when you select…

NCM has not yet been updated for SWISv3, so you will need to connect to SWISv2 to call Cirrus.Nodes.AddNodeToNCM. Just take the "/v3" out of the endpoint address.

The entity names are the same. What is the difference between what you are getting from that query in EOC vs. SAM?

It's still there - it has just turned into a button in the upper right corner of the useful/pleasing page. You shouldn't need to use it very often though - the cache is supposed to be self-maintaining.

A query like this should work: SELECT c1.NodeID, c1.DownloadTime, c1.ConfigFROM Cirrus.ConfigArchive c1INNER JOIN ( SELECT c2.NodeID, MAX(c2.DownloadTime) AS DownloadTime FROM Cirrus.ConfigArchive c2 WHERE c2.NodeID IN (SELECT NodeID FROM Cirrus.Nodes WHERE NodeCaption LIKE '%DSW%') GROUP BY NodeID) c3 ON…

That's the normal return value. It doesn't indicate a problem. Without seeing your code, I'm guessing what the issue might be. Are you sure the time range you specified overlaps with "now"? Remember, you need to specify times in UTC.

There is a verb that might do what you want. It was missing from the https://github.com/solarwinds/OrionSDK/wiki/Alerts​ page on the wiki, so I just added it. It looks like this: Orion.AlertActive.ClearAlert One parameter: int[] alertObjectIds To clear an active alert manually, pass the AlertObjectID values to…

The problem may be the use of the "ADDHOUR" function. See the note at the bottom of this page: NTA 4.0 Entity Model · solarwinds/OrionSDK Wiki · GitHub Try doing the date math using + and - fractional days instead of the functions. Like this: WHERE Flows.ObservationTimestamp > GETUTCDATE() - 0.417

Right now there is no plan to rebuild SP3, so this is it.

How would we identify templtes and development VMs?

Have you tried adding your view type to /Orion/Orion.config instead of making a new .config file? The website infrastructure expects those config files to correspond to a "real" module, which ties into installation, licensing, some stuff in the database, etc. I think it's going to be an uphill battle to get that working as…

I don't think you need to create a module to add some custom pages to the Orion website. Also, I'm not sure I understand why you would need to create a new view type. Why not just add your custom resources to a Summary view?

We are planning to significantly improve this API area, but it is not in the current release.

What issue were you having with the SWQL? Querying Orion.Credential should have worked...

Chris, In 9.0 we made some improvements to the handling of unicode characters in the website. Do you still have a 9.0 system around to try this on?

Start here: Home · solarwinds/OrionSDK Wiki · GitHub

It's probably best to handle this issue through support. Have you opened a ticket yet?

There was a space at the end of the link. I edited Brandon's post to fix it. Please try again.

Let's start with the website timeout issues. In \Inetpub\Solarwinds\web.config, find the <threshold value="WARN"/> line and change the value to DEBUG. Save it. Click around the website until you hit a timeout or two. That will capture more information about what the website is busy doing when it gets bogged down. Capture…

We've seen this issue too. It will be addressed in hotfix 2.

You can join this chain: Orion.AlertConfigurations -> Orion.ActionsAssignments -> Orion.Actions -> Orion.ActionsProperties. Like this: SELECT AC.AlertID, AC.Name, AA.Action.ActionID, AA.Action.Title, AA.Action.Properties.PropertyName, AA.Action.Properties.PropertyValue FROM Orion.AlertConfigurations AC LEFT JOIN…

What version of NCM are you using?

What version of NPM are you using?

This seems to be a bug in NPM 12. I reproduced it easily and was not able to find a direct workaround. I put it our bug tracker as issue CORE-6828. A more elaborate workaround would be to use the discovery API to add the nodes instead of creating instances of Orion.Nodes directly.

Your assumptions are all valid, but there is a problem with the way the SWIS schema for NCM.NodeProperties is set up that prevents the "read" operation from working with it. I recommend you stick with the query interface when you need to deal with NCM NodeProperties.

Ok, let me know what you find.

Alex, could on that error page, please click "Save Error Report Locally". You'll get a text file containing the exception stack trace and some more details. Attach it to this thread and I should be able to figure out what is going wrong here.

We were unable to find a workaround, but we do have a fix. It should be in the next release. If you decide to talk to support about it, reference CORE-6507.

That's weird. I would just open a ticket with SolarWinds support for that one.