tdanner ✭✭✭✭✭

You can pass datetime values as strings if you put them in quotes. SWIS will convert them from strings to datetimes. But in my scripts I prefer to operate on them as powershell datetime values. Like this: [datetime]$start = '2017-02-10 12:00:00 AM' [datetime]$end = '2017-02-20 12:00:00 AM' (I also prefer the year-month-day…

I sent your question to the SAM dev team to see if they have any suggestions.

> If you pipe set-swisobject to $uris, you are still looping through each object in the collection and invoking the piped command This is not the case. Consider these two powershell commands: #1 - $uris |% { Set-SwisObject $swis $_ -Properties @{UnmanageFrom=$start;UnmanageUntil=$end} } #2 - $uris | Set-SwisObject $swis…

The SwisClient class is just a thin wrapper around requests - I would not expect any behavior difference between these two. But SwisPowerShell uses a different channel to talk to SWIS and there are some differences in how authentication is handled. In characterizing this bug, it would be helpful to know if, in your…

Ok, that makes this easier. If you clear out the Caption and FullName fields in the database for those interfaces, Orion will regenerate them a few seconds later using the current interface alias value. What you need to do is build a SQL SELECT query that grabs the interfaces whose names you want to reset. It's ok if it…

I've seen people advocating for both behaviors (nulls go in the Unknown group and nulls go "loose"), so I think I'll just make it configurable by clicking Edit on the resource.

When I use a close equivalent to your code, without adding any pollers, I can open the node in the Edit Node page and see the credential there. But my test system is using the most recent release (Orion Platform 2018.4) while you appear to be using Orion Platform 2017.1. I don't know of anything that would have changed…

Like this: SELECT DISTINCT o.AlertConfigurations.Name AS [ALERT NAME] ,'/Orion/NetPerfMon/ActiveAlertDetails.aspx?NetObject=AAT:' + ToString(o.AlertObjectID) AS [_LinkFor_ALERT NAME] ,Case WHEN o.AlertConfigurations.Severity = '0' THEN ('/Orion/images/ActiveAlerts/Serious.png') WHEN o.AlertConfigurations.Severity = '1'…

Sorry for the late reply. In your "PluginConfigurationItem", you have included the entire server response, headers and all: {"PluginConfigurationItem":"HTTP\/1.1 200 OK\r\nContent-Length: 2014\r\nContent-Type: This string should only have the XML (the response ​body) not the response headers.

I added your vote to our bug for this issue and notified the product manager.

We're making incremental improvements, but there's no comprehensive API guide project that will "come to fruition very soon".

Have you looked at this page? Alerts · solarwinds/OrionSDK Wiki · GitHub

It's in "Orion SDK.pdf", which is linked from the start menu as "Technical Reference".

Are the two servers running the same version of NPM?

Could you post the code that produces that error?

For calling AddJob through SWQL Studio or PowerShell, the XML format for an NCMJob object would be needed. For REST, json format would be needed. The NCMJob object is pretty complex - it has dozens of fields, some of which are sub-objects with still more fields. This API was, frankly, not designed with customer use in…

That sounds like a bug. Can you post details - the full Uri and the full set of properties you are setting? I'll pass it to the IPAM team for investigation.

NPM 11.5.1 has been released. It addresses this bug. If you have NPM, you can upgrade to that to get this fix. If not, the equivalent fix for SAM will be in the next SAM update. This fix was not included in NPM 11.5.1. It will be in 11.5.2 when that comes out.

Ok, I found the details for turning off hardware health monitoring. There's a separate verb for controlling this: Orion.HardwareHealth.HardwareInfo.DisableHardwareHealth. It takes one parameter: a net object id. Those look like "N:123" where 123 is the NodeID. So from python you could call it like this:…

This was fixed in IPAM 4.7.

Instead of constructing the uri, just ask SWIS for it: $nodeCpUri = Get-SwisData $swis 'SELECT N.CustomProperties.Uri FROM Orion.Nodes N WHERE N.SysName = @s' @{s=$sysname} Set-SwisObject $nodeCpUri @{DEVICE_LOCATION = 'test'}

dkeyser, what version(s) are you seeing this on?

See the bottom of this page: SAM Application Monitoring Templates · solarwinds/OrionSDK Wiki · GitHub You may be able to use this to achieve that.

This question was specifically about SAM Application monitoring. Are you asking about monitoring for network quality of service, like DSCP or cbQoS?

Yes, this was a change between beta and RTM. These extra fields were added to improve UI performance. I'm looking at how we can simplify the API back to what it was in the betas, since these fields can be calculated or looked up just given the ParentUri and ChildUri for the dependency.

No web.config file? That's a real problem. Are you sure you're looking in the proper directory for your website? If so, it's time to look at the ConfigurationWizard.log file (it's in Program Files\Solarwinds\Orion). 

Sorry, no update here.

This is a known problem with hotfix 2. It will be fixed in 8.5.1, but here's a workaround that will get you running again. Edit \Inetpub\Solarwinds\Orion\custom.config and change the port to 443. 

Thanks for the pointer. I'll get that article updated, because that wording is misleading.

Yes, this is possible. The samples in OrionSDK/Groups.ps1 at master · solarwinds/OrionSDK · GitHub show all of those basic operations. You would just need to write some loops to handle the logic for your organization and naming convention. Let me know if you have issues.