tdanner ✭✭✭✭✭

There are a few query features that don't work in SWIS when a query references data that spans multiple databases, and "WHERE NOT IN (SELECT ...)" is one of them. Fortunately you can rewrite this using a join instead of a subquery and then it should work. SELECT Caption FROM Orion.Nodes orionnode LEFT JOIN NCM.Nodes…

I don't know of a way to do this with NPM, but APM can certainly handle monitoring TCP ports.

Like this: SELECT '<span style="color:' + CASE Status WHEN 0 THEN 'red' WHEN 1 THEN 'green' WHEN 9 THEN 'purple' ELSE 'black' END + '">' + Caption + '</span>' AS ColorCaption FROM Orion.Nodes

This has been fixed in NPM 12.4. ifAdminStatus and ifOperStatus are now reported correctly for DiscoverInterfacesOnNode.

The duplicate records are a known issue (IPAM-606). You should be able to work around that by changing the query from SELECT to SELECT DISTINCT. For the failed queries, try adding "ORDER BY 1" to the end of the query.

In 9.1 we added Location (and Contact and maybe some others) to web node management. For your additional web server, it sounds like your schema files didn't get updated properly for your custom properties. If you run Custom Property Editor on the web server, add a temporary dummy property and then delete it, it will update…

Then I think the operation you want is "PollNow". In PowerShell, that looks like this: $swis = Connect-Swis -Hostname localhost -Username admin -Password "" $nodeId = 123 Invoke-SwisVerb $swis Orion.Nodes PollNow @("N:$nodeId")

Could you start a new thread with a description of the issue including versions and specific errors?

HOURSDIFF will always return an integer. If you want the different in fractional hours, use MINUTEDIFF and divide by 60.0 (not 60). That will cause the division to be done in floating point.

Orion can trigger actions in response to syslog or SNMP traps, but alerts are only raised for an alert definition/monitored object pair. If the syslog actions are not sufficient for your needs and you require a persistent alert, then there are a few options. One way to do it would be to create an Orion node for each…

One of the things this mapping table is used for is to guide constructing the net object id string (like "N:42") from a SWIS entity instance (like an instance of Orion.Nodes with a bunch of properties, including NodeID=42). This net object id string is used in a few places, most notably website navigation. If you have a…

Better open a support ticket in that case.

The first log to check is the SWIS log: C:\ProgramData\SolarWinds\InformationService\v3.0\Orion.InformationService.log. That wasn't enough to figure it out, but it did point me to the code that was throwing the exception. I followed that to see that it was making a call to the NPM business layer service, which has its own…

If those log messages are what I think they are, you are probably getting them continuously in the logs whether you are running that script or not. You probably have an issue with RabbitMQ or connectivity between your polling engines on port 5671. SWIS has fallback mechanisms in case there is an issue with RabbitMQ, so…

I tried this on my Orion installation. It loaded fine in Firefox and Google Chrome, but failed to load in IE6 and IE8. I didn't get the popup about saving the js file - it just didn't fill in the Tube status widget. What browser(s) have you tried?

What is the value of "nodeId"?

There's no API support for editing basic alerts. If you don't mind continuing the conversation, is there anything blocking you from moving to the new web-based alerting system in NPM 11.5?

Normally Orion pings each node every two minutes and puts one row in Orion.ResponseTime. If the ping succeeded, PercentLoss = 0 and Availability = 100. If the ping fails, it will switch to "fast polling mode" - 1 ping every 10 seconds until it gets a response or two minutes are up. If it gets no response, PercentLoss =…

Call the sales number and they'll hook you up with someone who can help.

Orion.NPM.CustomPollerLabels was added to SWIS in NPM 10.7.

As the fourth column in the SELECT clause, you have this: "Details" = Case ... END This is not the normal SWQL syntax for column aliases (which follows standard SQL). It should look like this instead: Case ... END AS Details I found another issue. This function call works in SQL, but not SWQL: DATEADD(DAY,-1,GETDATE()). To…

If your production database is too overloaded to support development, you might want to set up a copy for testing. You can use a trial license of NPM with SQL Express. Take a backup of your production database and restore it to SQL Express.

That helps, but there are more choices to make. Do you just want a one-way forwarding? You could do that by creating a trigger action on each alert definition that calls a script that generates a fault in your other system. Or you could create a program that runs on a regular schedule and queries Orion for active alerts…

Yes, AD groups are supported. Can you log in to the web console as that domain user? For SWQL Studio to connect as a domain user, you can use the "Orion (v3)" server type option and the "domain\username" format in the "User Name:" textbox.

How about just using the regular Node Tree resource with a filter? Just click the Edit button in the upper right of the Node Tree and put "Status=1" (for down nodes) or "Status<>0" (for all nodes that aren't up) in the "Filter Nodes (SQL)" box.

You should have three InterfaceTraffic tables: _Detail, _Hourly, and _Daily. There's also an InterfaceTraffic view that is the union of these three tables. Is that what you have?

There's not really a way you could have found this. What we need is a page on the github wiki that documents the discovery API, but we don't have that yet.

For Perl, we don't have any documentation beyond the comments in the sample script and posts on this forum.

Hopefully this will get you started. Install SUDS - I used this version: https://bitbucket.org/jurko/suds from suds.client import Client url = 'https://localhost:17778/SolarWinds/InformationService/v3?wsdl' swis = Client(url, username='admin', password='') swis.set_options(port='BasicHttpBinding_InformationService')…

In general, any language or runtime should be able to connect to the SolarWinds Information Service - you aren't restricted to the languages we provide samples for. You just need to choose a SOAP client toolkit for Python. I haven't tried that myself, but I would start with Suds.