Comments
-
That post is from 2014 and uses the old API. Your json is close, but you need to remove the parameter names. Just send the values. Like this: [ [ 146735 ], "Incident undefined..." ]
-
Have you tried connecting with SWQL Studio using the "Orion over HTTPS" server type?
-
That readme line is referring to a specific issue that actually broke the whole VoIP Summary page - it wouldn't load at all; you would just get an exception. Since that's not what you're seeing, you probably have a different issue. Time to hit support.
-
That is a very well-written feature request! The best way to get it in front of the right product managers would be to repost it over here: Network Performance Monitor Feature Requests
-
Let's continue this discussion in your other thread: Solarwind API
-
That verb relates to the old "advanced alert" system. The current alert system is documented here: Alerts · solarwinds/OrionSDK Wiki · GitHub . Acknowledging alerts is discussed near the top.
-
Volume filtering is not available through this interface. The best you can do is just let discovery import all the volumes and then delete the ones you don't care about.
-
Do you mean a more up-to-date MAC address than what UDT recorded on the last polling interval? There's no API for "fetch it live".
-
There are many options for exporting data about nodes. To get that data into a specific XML for that ManageEngine will take, you are probably going to need to write some code. If you can give me more information about the workflow you have in mind and your preferred programming language(s), I can give you more detailed…
-
SwisPowerShell provides powershell cmdlets for the fundamental operations: connect, query, invoke, create, update, delete. PowerOrion provides higher-level operations like "New-OrionNode" and "Get-HostNameFromIPAddress". PowerOrion uses SwisPowerShell internally.
-
Here's a simple python script that returns what IPAM has for a given IP address. Half of the code here is just looking up the set of custom fields. import requests from orionsdk import SwisClient requests.packages.urllib3.disable_warnings() hostname = 'orion-server.local' username = 'admin' password = '' ip = '1.1.1.1'…
-
* Following the PowerShell guidelines, Connect-Swis takes a PSCredential object for the username and password. If you want to put the password in your script in clear text, here's how to make a PSCredential from a username and password from…
-
What kind of issues are you having?
-
There is currently no direct way to connect a new entry in Orion.Nodes with the corresponding entry in Orion.DiscoveredNodes. Matching by IP address and EngineID is about the best you can do. It's a good idea though.
-
The version of InformationService.pm distributed with the SDK doesn't have the Invoke operation hooked up correctly. I have updated it and attached a new copy to this reply. I also added an example of how to use it to unmanage a node. To add a node to NCM, the call would look like this: $swis->Invoke('Cirrus.Nodes',…
-
That field is limited to 255 characters. If you have more than a few sentences, I recommend you just put a link to the full text somewhere else. You can use normal html tags (<a href="...">...</a>) in that field.
-
What happens if you use the "-Trusted" option in Connect-Swis instead of typing in a username and password?
-
Looks like a bug. I'll try to get it fixed in 8.5.1. The only workaround would be to use Database Manager to set the Title column in the Resources table for that resource. When you click the edit button on the resource, you can find the resource ID in the URL - that will tell you what row to edit in Database Manager.
-
Thanks. I have entered this bug into our system.
-
Are you sure that's the correct NodeID? And that it still exists? That's the error you get when you try to delete something that doesn't exist. (We should fix that to be a 404 error instead of 400.)
-
There's no relationship defined between Orion.ContainerMembers and Orion.Nodes - this is why the alert designer doesn't offer to link them together. However, you are correct that you can use a "Custom SWQL" alert to get around that by using a custom join. Here's something to get you started: SELECT Nodes.Uri,…
-
The "servername.wbmason.corp" part of the SWIS Uri is a "system identifier" that is used to identify this Orion instance. It is not used as a hostname for addressing purposes, just as a way to tell NodeID 890 on this Orion system apart from NodeID 890 on some other Orion system. When you first install (specifically, when…
-
Try this: * Rename \Inetpub\Solarwinds\Orion\custom.config.txt to custom.config * If IIS is listening on just a single specific IP address, edit custom.config and replace "localhost" with that IP address. If IIS is listening on all IP addresses, just leave it as "localhost". * Restart IIS
-
Have you looked at this page? REST · solarwinds/OrionSDK Wiki · GitHub
-
I don't see anything obviously wrong with that script. It looks like it should set the custom properties fine. What happens if you add $ErrorActionPreference = 'Stop' to the top of the script? If you look in C:\ProgramData\SolarWinds\InformationService\v3.0\Orion.InformationService.log on the Orion server after running the…
-
This page provides instructions on how to install and import SwisPowerShell, the module that provides Connect-Swis and the other cmdlets in this script: PowerShell · solarwinds/OrionSDK Wiki · GitHub
-
We don't currently have an API for that.
-
How about something like this? 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 WhoFROM Orion.Nodes NLEFT JOIN Orion.AuditingEvents AE ON N.NodeID =…
-
Start here: Home · solarwinds/OrionSDK Wiki · GitHub
-
Can the 3rd party integration be updated to use SWISv3 instead?