tdanner ✭✭✭✭✭

You can use the "ToLocal" function to translate from UTC to the time zone of the server processing the query, or the "AddHour" function to translate to a specific time zone. See SWQL Functions · solarwinds/OrionSDK Wiki · GitHub for a list of available functions.

Excellent point! Here's my query changed to refer to the audit event type by name instead of id. SELECT N.Caption AS NodeCaption, N.ChildStatus, N.Status AS NodeStatus, TOLOCAL(N.UnManageFrom) AS UnManageFrom, TOLOCAL(N.UnManageUntil) AS UnManageUntil, TOLOCAL(AE.ObservationTimestamp) AS UnManagedWhen, AE.AccountID AS Who…

That operation should cover both status and statistics collection.

In that case, this error could be caused if the account you are PowerShell running under does not have rights to read that private key. If User Account Control is turned on in Windows and your PowerShell process is not elevated, that can also interfere. Options: use an elevated local admin context for PowerShell or switch…

Right - it should have updated the report schemas automatically. In 9.1 we made a point of testing that case because it's something we've had issues with in the past. But as you can see (sadly), you and others are still having the problem this time around.

I checked this out. It turns out that there were two IIS websites configured pointing to C:\InetPub\SolarWinds\Orion. The one that was actually being used was missing the URLRewrite.dll ISAPI filter. We deleted the unused one and added the filter to the real one and things started working right.

No, I don't think this will be possible - you can edit the message that gets added to Orion.Events when the alert resets, but we don't have variables defined for all of those properties. Maybe when you see a new alert triggered you can record those properties in some other storage, then when the alert resets you can look…

This is pretty basic (very few properties have the description filled in), but it does at least list everything: SolarWinds Information Service v3.0 Schema Documentation Index

The only required parameter is the sql query, as a string. You can omit the rest.

That's a good fix. This property validation is new in the 2015.1 version of the platform. (Thanks, madhavan!) You can now leave out all of those default values in your script (where you used to have to provide empty string for a lot of properties) and the property validation will fill them in.

I added your vote to the internal feature request for a supernet/group creation API. It's "IPAM-705" if you need to check on the status of it.

I've gone through the code and tried a few experiments - I can't find any expression that works as an equivalent to "Property IS NULL".

The NodeIDs that the NCM verbs expect are NCM node IDs, which are GUIDs (like "244d5b4a-0cd1-444d-ba87-d185252eaa4c"), not ints. DownloadConfig expects a list of NodeIDs and a config type name (string). In python, that would look like this: nodeId = '244d5b4a-0cd1-444d-ba87-d185252eaa4c' nodeIds = [nodeId] configType =…

As for the config types, the default ones are "Running" and "Startup". You can define custom ones on /Orion/NCM/Admin/Settings/ConfigSettings.aspx.

I'm glad to hear that!

Your formatting looks fine. That error doesn't really make sense to me. But if you look in the SWISv3 log file (C:\ProgramData\SolarWinds\InformationService\v3.0\Orion.InformationService.log) it should have a stack trace to go with that error. With that hopefully I can figure out what is going wrong.

No, the subscription system is not for customer use at this time. You can use a trigger action to run a command line when an alert triggers. This can query for whatever additional context properties you need and call other systems' APIs. A similar reset action can be used to clear alerts in other systems.

Unfortunately, NPM 12.1 does not handle the booleans in json correctly. See 400 Client Error: Specified cast is not valid · Issue #9 · solarwinds/orionsdk-python · GitHub . If you can use PowerShell instead, that works.

Once the interfaces have been added, you can rename one like this: Set-SwisObject $swis $uriOfTheInterface @{Caption=$theNewInterfaceName} You will need to get the Uri of the interface you want to rename. You can do that this way: $uri = Get-SwisData $swis "SELECT Uri FROM Orion.NPM.Interfaces WHERE xxxxxx" Replace xxxxx…

That's very odd. And IPAM is actually installed? Do you see the IPAM xml file in C:\Program Files (x86)\SolarWinds\Orion\Information Service\3.0\Schemas?

Ok, it looks like due to some internal changes, you now need to put the "0+Status" expression in the SELECT clause as well when you use it in the ORDER BY clause.

A 500 error should leave some details in the log on the server. Look in C:\ProgramData\Solarwinds\InformationService\v3.0 and see if that gives a clue.

Look at the results of this query and see if it clears things up: SELECT ID, Name, Description, CredentialType, CredentialOwner FROM Orion.Credential WHERE Name='the name in question'

The easiest way to see what Orion SP you are on is to look at the website footer. If it doesn't say SP such-and-such, then you don't have any Orion service pack installed.

No update here. This is still not supported.

Are you choosing SNMP for status and response time intentionally? The ICMP pollers for status and response time are generally more accurate since they are not affected by the performance and availability of the target's SNMP agent. We provide them for networks that do not allow ICMP. Also, don't assign the volume pollers…

I don't see any clues there (I assume the lack of space between the URL and "HTTP/1.1" is just a copy and paste error in forum reply, not the actual request), so let's look at the log. Examine C:\ProgramData\Solarwinds\InformationService\v3.0\Orion.InformationService.log right after triggering the error and see what you…

Of note - in Orion Platform 2017.3 (a.k.a. NPM 12.2) we put some work into improving the performance of many aspects of Orion Groups. They still aren't "free", but they are cheaper than they used to be. Larger and more numerous groups should have a smaller systemic impact than in previous releases.

Here's a sample for adding a WMI node via PowerShell: OrionSDK/CRUD.AddWMINode.ps1 at master · solarwinds/OrionSDK · GitHub If you have questions about doing the same operations from Python, let me know. The WMI credential is associated with the node though an entry in Orion.NodeSettings with SettingName="WMICredential"…

The request body for all POSTs to .../Invoke/... needs to be a JSON array. Just wrap your current input in [brackets] and try again.