Comments
-
This is still not supported in the IPAM API.
-
marcnetterfield brought an issue to my attention that I missed when responding in this thread last year: 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>…
-
Where you have this line: $InterfacesPluginConfiguration = Invoke-SwisVerb $swis Orion.NPM.Interfaces CreateInterfacesPluginConfiguration It should be this instead: $InterfacesPluginConfiguration = Invoke-SwisVerb $swis Orion.NPM.Interfaces CreateInterfacesPluginConfiguration @($InterfacesPluginConfigurationContext) Also,…
-
I don't know much about PHP (except for Austin's Pint House Pizza), but I think the problem is this line: $core_plugin_data = array('context' => "$updated_core_plugin"); For sending to an Invoke call, we need a JSON array, not a JSON object. Try this instead: $core_plugin_data = array($updated_core_plugin);
-
If you clear the Node Name field (the Caption column in the Nodes table in the database), the poller should fill in the new name for the switch.
-
SELECT FullName FROM Metadata.Entity WHERE FullName LIKE '%alert%'
-
Orion's Capacity forecasting feature is based on a linear fit of the historical data using one sample per day. The linear fit equation looks like this: [projected value] = A + B * [days after start] The product has two methods for choosing one historical sample per day: "avg" and "peak". In the "avg" method, it takes the…
-
PowerShell remoting is kind of magical (which is another way of saying complicated and error-prone!). But I suspect the actual problem here is that the exported SecureString is not portable from one computer to another. So when you copy the long number produced by ConvertFrom-SecureString and paste it into the remote…
-
Connecting to SWIS through the SDK is the recommended way to get data out of Orion. "JToken" comes from Newtonsoft Json, which is the most popular .NET library for working with json-formatted data. I recommend you get familiar with it if you are going to be working in C# - it comes up everywhere.…
-
We're looking into the hardware health issue and will respond when we have a more complete answer for you. Regarding the need for a straightforward and complete way to add nodes via the API - I agree. We are not there yet, but it is high on my list.
-
If I understand correctly, I think a query like this should get you started: SELECT DATETRUNC('month',rt.DateTime) AS d, n.Caption, AVG(rt.Availability) AS Avail FROM Orion.ResponseTime rt INNER JOIN Orion.Nodes n ON rt.NodeID=n.NodeID WHERE n.CustomProperties.Department = 'Enterprise Servers' GROUP BY n.Caption,…
-
That's basically correct, but you don't do it with an "update where" query - SWQL only does SELECT. To modify the data, first get the Uris of the objects to modify, then call an Update operation on them. In PowerShell you do this via the Set-SwisObject cmdlet. Something like this: $swis = Connect-Swis [connection options…
-
To add a member to an Orion group, you need to call the Orion.Container.AddDefinition verb. Here's some perl code for doing that: use SW::InformationService; use SOAP::Lite; use XML::LibXML; my $hostname = "localhost"; # fill in a hostname my $username = "admin"; my $password = ""; my $groupID = 3; my $nodeID = 3; my…
-
This is a known issue with 8.5 See also this thread.
-
What version of NPM are you using? What version of Visual Studio?
-
The JSON API is a SWISv3 feature, so it doesn't work for SWISv2. When NCM ships their SWISv3 update, you will be able to query NCM data using the JSON API.
-
This is a bug in how SWIS formats DateTime values in JSON. I reproduced it. As a workaround, you can wrap the DateTime property or expression in "ToString()".
-
No, SAM 5.2 does not have a verb for rediscover. NPM 10.4 adds some verbs that give you some control over the network discovery process. I expect that this functionality will make it into SAM at some point, but I can't make any promises. I also couldn't say whether that will cover your needs without more details.
-
Are your basic auth credentials valid in Orion? Do they work in SWQL Studio?
-
You have a few things to figure out: 1. Fetching data from SolarWinds. Start at https://github.com/solarwinds/OrionSDK to get oriented and ask questions here. 2. Writing data to ScienceLogic. I can't help you with that. 3. Mapping entities and fields between the two systems.
-
You are close. Your second query would be written like this: Select N.Interfaces.Availability.Weight From Orion.Nodes N (Careful - interface availability is a history table. Selecting from it with no TOP or WHERE clause may produce a huge result set.)
-
Please see this thread: Active Alerts - Creating a duplicated view
-
The current version of the product does not support this, but the beta of NCM 7.2 does. In NCM 7.2, you can search configs using the Cirrus.ConfigArchive.ConfigSearch verb. It takes seven parameters: * Search query (string) * Config type (string) - like "running" or "startup". * NodeIDs (string) - either the empty string…
-
As you have noticed, all the "Done" button really does is take you back to the list of views. I can't think of any good solution to this. Your best bet might be to just copy the view you want to edit, make all your changes, and then update pointers from the old view to the new one (in account settings,…
-
What data are you trying to get? I would assume that a normal query would work for you. Like: SELECT ...a few fields... FROM Orion.Nodes WHERE NodeID IN (...1700 NodeID values...)
-
No. Unfortunately, the IP Address Details View does not support these kinds of macros in the custom query resource.
-
Yes, this is in 9.0. To hide a module from a user, edit that user account in the website. Expand <account name>'s VoIP Monitor Settings (or Wireless or whatever) and set the VoIP Summary View to 'None'. If you hide all of the installed modules from a user, they won't see the Modules bar at all.
-
There are three issues with your XML. First, it needs to be in the right namespace. For this object, that is 'http://schemas.solarwinds.com/2007/08/APM'. Second, the Frequency and Timeout values are TimeSpan objects, which use the ISO 8601 duration format. 350 seconds is 5 minutes and 50 seconds, so that would be PT5M50S.…
-
Those do sound useful. Why not post this in Network Performance Monitor Feature Requests where it can collect votes?
-
The <properties> element also needs xmlns="">schemas.solarwinds.com/.../informationservice". Was that namespace on your original request and just removed for readability?