dan_jagnow · Senior Architect

I have confirmed that the API should not require node management rights. The request to change that behavior is being tracked as internal issue CORE-12986.

Orion.APM.ComponentSetting now supports an update operation (internal issue SAM-7007) with the SAM 6.8 release.

It seems that the site has some internal errors at present. If you use the site's internal search functionality, you'll see that the articles are still indexed there, but the links don't work. https://www.networkmanagementsoftware.com/?s=solarwinds+orion+api However, through the magic of the Internet, you can still access…

From what I can tell, this is not supported yet. The internal ticket number is now SAM-7966 instead of 348041.

I suggest reading through the documentation at Migrate SolarWinds Orion products to a new server with a new IP or hostname . The hostname appears in several places in the Orion database. Until all of those references get updated, your SWIS URIs in the replicated environment may end up sending you back to the original host.…

You probably want information from the Orion.Events table. See this for an example query: Node Downtime with Duration and Minimum Length Filtering

You're right, antonis.athanasiou. I should have included a link to tdanner​'s response on this thread: Change SolarWinds Information Services SSL Certificate Note that this is a manual process that involves editing configuration files, and which will be overwritten whenever you run the Orion Configuration Wizard (including…

Thanks. I was able to reproduce this error (valid SWQL failing when used in a Custom Query resource). This being tracked with internal issue CORE-13219.

It's really close. It needs a closing single quote before the comma, and the x, y, z IP address need to be enclosed in quotes: swis.query('SELECT Uri FROM Orion.Nodes WHERE IPAddress IN @ip_addr', ip_addr = ['x', 'y', 'z']) And, of course, they need to be actual IP addresses.

I have looked through the source code, and it seems that the UpdateUsernamePasswordWithContentCredentials verb can only be used with Palo Alto credentials at this point in time.

You can perform CRUD operations on many of the entities that SWIS provides, but updates don't work like SQL UPDATE statements, where you can specify the nature of the update operation to perform and the filtering logic in a single statement. Instead, you would need to perform one query to identify the nodes where the…

Did you try the DateTrunc function? See https://github.com/solarwinds/OrionSDK/wiki/SWQL-Functions

From SWQL Studio you can view the Web Browse Template settings as follows: SELECT NodeID, SettingName, SettingValue, NodeSettingID FROM Orion.NodeSettings WHERE SettingName = 'Core.WebBrowseTemplate' To add this setting when you add the node, you can add a little code like this after you've retrieved the nodeid. # set up…

As tdanner​ suggested, you should try reading the the SWIS log file on the Orion server right after a failed request from one if the instances where Windows Authentication is not working: C:\ProgramData\SolarWinds\InformationService\v3.0\Orion.InformationService.log You can test the connection to SWIS with a very simple…

When you say that the script doesn't work for you, do you mean that the script throws an exception, or that the script completes without error but does not seem to perform the update? If you're encountering an error, could you include the error details?

> How can we customize it to avoid resources we don't want ? Such as 'windows scheduled tasks', physical/virtual memory as volumes, unknown interfaces ? I don't believe it is possible to filter the set of resources to import at present.

This is now being investigated under https://github.com/solarwinds/OrionSDK/issues/223.

Communication with the API occurs via Windows Communication Foundation (WCF). You may be able to find some additional details about the error in the Event Log. See https://intrepiddeveloper.wordpress.com/2008/08/07/security-event-logging-auditing/ for more information. If that doesn't lead you to answers, it might be…

It looks like things are fine down to this... schannel: Curl_read_plain returned CURLE_RECV_ERROR ... Send failure: Connection was reset schannel: failed to send close msg: Failed sending data to the peer (bytes written: -1) I wonder if your network connection to the Orion server is spotty for some reason. When attempting…

This approach looks good. I haven't used OTRS before, but you should also try taking a look at the system log to see if it provides any details about what caused the internal error.

To get some details from the SolarWinds Database Manager on the enabled alerts with associated actions that send emails, including what SMTP server they are configured to use, you could do something like this: SELECT ac.AlertID, ac.AlertMessage, ac.Name, ac.Description, ac.Enabled, ac.ObjectType, ac.NotifyEnabled,…

The Orion platform has been releasing twice per year (major releases during Q2 and Q4 in recent history), but I can't make any specific commitments about the timeline for this issue.

Yes, the issue is classified as a bug. There is more detail about the history of this issue here: Re: Question about granting rights for SolarWinds IPAM API

The permissions for these Orion verbs correspond to the permissions used when you perform the equivalent steps from the Orion UI (when logged in with the same account). Permissions can be defined per user from the UI.

It could be a problem with the SELECT DISTINCT. See Re: Using custom SWQL to search for subnets.

AlertDefinitionsView is a view, not a table. However, I may have misunderstood what you are looking for. I suggest reading the documentation at Alerts · solarwinds/OrionSDK Wiki · GitHub to get a better understanding of how alerts work in Orion. If you are interested alerts that are currently active, then you can run a…

> The provided PowerShell script returns "True" with the domain controller name, so it is connecting to the domain successfully. What happens when you use the domain name instead of the domain controller name?

Interesting... What happens if you revise the PowerShell script to use the "Machine" option instead of "Domain" when creating the PrincipalContext​? $pc = New-Object System.DirectoryServices.AccountManagement.PrincipalContext @("Machine")

If you're interested in making changes to custom properties, you'll want to read the Modifying Custom Properties​ section of this page in the wiki: Managing Custom Properties · solarwinds/OrionSDK Wiki · GitHub

I don't see anything obviously wrong with the format of your query. Have you tried removing the WHERE clause to see if you get data back? You may also find it helpful to install SWQL Studio (https://github.com/solarwinds/OrionSDK/releases​), which makes it easier to explore the data that Orion has to offer. You can test…