Comments
-
Just email it to me.
-
Yes, it is searching for a literal expression. No wildcards or regex. This follows the behavior of the SQL "replace" function. For performance reasons it is best for us to stick to functionality that can be handled in SQL and not in our code. Orion Platform 2018.2 (currently in beta) adds the "charindex" function to SWQL.…
-
Not directly, but there are samples for querying data and for deleting items.
-
If you have it working on one server but not another, I would look for differences in the versions everything python-related on those two servers. Do they have the same versions of python, requests, openssl, etc.?
-
That is correct: these tables do not support modification through the API. lputcha - have you tried reaching out to cobrien? I think he would be interested in discussing this with you.
-
There's another timeout that we might be hitting. In C:\Program Files (x86)\SolarWinds\Orion\NPM\SolarWinds.NPM.BusinessLayer.dll.config, find this section: <binding name="NPM.NetTcpBinding" sendTimeout="00:05:00" maxBufferSize="2147483647" maxReceivedMessageSize="2147483647" portSharingEnabled="true"> <readerQuotas…
-
Is this fixed in SP1? Our Orion takes a good 5 minutes to stop the service. In Task Manager, I watch memory usage slowly tick down from about 218M avg to around 170+/-M and finally, poof, it's gone. This is a longstanding quirk of with the way the NetPerfMonService handles shutdown. We didn't touch that in SP1.
-
This is fixed in Orion Platform 2018.2 / NPM 12.3, out today.
-
Yes. For historical reasons, NCM has its own NodeID in GUID format. The config transfer verbs work with these NCM NodeIDs. You can find the NCM NodeID guid given a regular Orion NodeID int with query like this: SELECT NodeID FROM NCM.Nodes WHERE CoreNodeID=123
-
Let's look at the SWISv3 log file. It will be on the Orion server at C:\ProgramData\Solarwinds\InformationService\v3.0\Orion.InformationService.log. To make it easier to find the problem, trigger the error from PowerShell immediately before copying this file. Then open it up in notepad and copy out the lines around the…
-
It should work with or without the xml declaration line.
-
There is no document explaining all the available verbs. Some are documented in the SDK doc (Orion SDK.pdf) and some are documented in the samples.
-
Can you post the script you are using?
-
The way IPAM custom properties work, you have to create the IPAM.IpNodeAttr object if it doesn't already exist. See https://github.com/solarwinds/OrionSDK/wiki/IPAM-4.6-API#crud-operations-for-ipamipnodeattr for how to do this.
-
It's very strange that the error would go away just from changing the log level. I can't explain that. I'm also not sure what is causing the error you are seeing in the log, but I would not expect it to prevent the unmanage operation from completing correctly. After you call Unmanage, can you check the properties of the…
-
This functionality has not changed in the last year.
-
These culture differences are making this harder! Let's try this: ${SQL: SELECT FORMAT(PARSE('${N=Alerting;M=AlertTriggerTime;F=DateTime}' AS datetime USING 'en-US'), 'dd MMMM yyyy hh:mm')} With this syntax we are telling SQL Server to use the US culture when converting the AlertTriggerTime from a string to a SQL datetime,…
-
We don't have a target date for an SDK update right now. Re: the Manage Windows Credentials page. That sounds very strange. We don't have an API for modifying the set of Windows credentials (just picking a pre-existing one for use with a WMI node), so it's not clear to me how this script could affect that page. Could you…
-
It doesn't matter where SWQL Studio runs, but that config file on server X controls the logging for queries processed on that server X. Queries processed on server Y will use the logging settings from the config file on server Y.
-
The Visual Studio Add Service Reference dialog will work with https://localhost:17778/SolarWinds/InformationService. It will warn you about the invalid certificate, but you can accept that and keep going. We recommend SOAP on :17778 for SDK users. net.tcp on :17777 is more for SolarWinds internal use.
-
Ok, hope you can get this sorted out.
-
Right - the IPAM 4.5 API does not yet cover supernets and groups.
-
It looks like it can't connect to port 17778. If the SolarWinds product is generally working, then we know what SWIS is running. So that implies a firewall issue preventing the connection. I would check on that. Another way to test this out would be to install the SDK on the SolarWinds server and try connecting locally.
-
I think I see the problem. You script is setting this variable: $EngineID = 1 But the script has this line: <EngineId>$EngindId</EngineId> That's a typo on https://github.com/solarwinds/OrionSDK/wiki/Discovery (I'll fix it as soon as I post this reply), but it could be the cause of this error. Orion is trying to…
-
marcnetterfield brought an issue to my attention that I missed when responding in this thread at the time: the syntax for credentials here doesn't work the way you would want it to. The correct syntax for using multiple credentials is: <Credentials> <SharedCredentialInfo> <CredentialID>1</CredentialID> <Order>1</Order>…
-
It sounds like you are doing everything right. I don't know why the Export to Excel option is not showing up. I made a simple custom report with your query and a simple custom table resource and the export worked. I recommend you open a ticket with SolarWinds Support.
-
What error?
-
The sample python script is already set to ignore invalid certs: verify = False if not verify: from requests.packages.urllib3.exceptions import InsecureRequestWarning requests.packages.urllib3.disable_warnings(InsecureRequestWarning) I think it is not getting as far as looking at the cert. I think python and curl might be…
-
So if I understand what you are looking for, you want to allow anyone to log in, but they should have to go past the login page with the legal message first. If I were implementing that, I would kill the DirectLink account and use a Guest account instead. Put the username and password in the Site Login Text so anyone who…
-
That's odd. This should work. Keep in mind that these times are set in UTC.