Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

How to query Node URI, Interface URI, and Volume URI from SQL

It doesn't appear that the SQL database has URI. I'm hoping to run a SQL query, but have it return a value for the URI (there are syntax limitations in SWQL, so I'm going to SQL).

swis://{pollingengine}/Orion/Orion.Nodes/NodeID={nodeID}

We've upgraded and migrated our Orion instance multiple times, so the value for my {pollingengine} is an old name for our original primary polling engine. Where is it getting that from? Anyone know what tables/columns would be used in a SQL SELECT to get:

Node URI
Interface URI
Volume URI

Find more posts tagged with

Accepted answers

All comments

tony.johnson

URI is a SWIS construct and is not stored in a dedicated column for each entity. The syntax is consistent so you will need to build these dynamically in SQL for later use. I am curious as to what limitations you are encountering with SWQL?

yaquaholic

From SQL you'll need to concatenate the various IDs to the following URIs:

Node URI

/Orion/NetPerfMon/NodeDetails.aspx?NetObject=N:<NodeID>

SQL: SELECT Caption, IPAddress, CONCAT('/Orion/NetPerfMon/NodeDetails.aspx?NetObject=N:', NodeID) AS URI From Nodes

Interface URI

/Orion/View.aspx?NetObject=I:<InterfaceID>

SQL: SELECT NodeID, Caption, CONCAT('/Orion/View.aspx?NetObject=I:', InterfaceID) AS URI From Interfaces

Volume URI

/Orion/NetPerfMon/VolumeDetails.aspx?NetObject=V:<VolumeID>

SQL: SELECT NodeID, Caption, CONCAT('/Orion/NetPerfMon/VolumeDetails.aspx?NetObject=V:', VolumeID) AS URI From Volumes

bhumphrey

Is that prefix:

swis://{pollingengine}

Not required? That was one of my sticking points. The {pollingengine} part is the FQDN of our original primary polling engine. Since then we've upgraded multiple times, migrated to two new domains, and added additional polling engines/HA/etc. But still the URI has the old name for some reason and FQDN, so it's not even coming from the OldEngines table.

bhumphrey

Hey Tony,

I just heard back on a different post on one of the solutions. I was having an issue with certain characters, but that can be gotten around with params. The other, I'm not quite sure on. Essentially, a way to utilize regex in a query. Something like this:

SELECT V.VolumeTypeID, V.VolumeType, V.VolumeDescription, N.Vendor, N.MachineType, N.Sysname
FROM Orion.Volumes V
JOIN Orion.Nodes N ON N.NodeID = V.NodeID
WHERE N.Vendor = 'Windows' AND V.VolumeTypeID = '0' AND V.VolumeDescription LIKE '\w:\\.*'

That last part for regex is where it fails.

bhumphrey

Hey @yaquaholic, just checking back here. Any chance you know where that first part comes from? The swis:{pollingengine} name?

yaquaholic

Try the DNS resolvable hostname for your Orion server, or the IP address.

yaquaholic

There's a database update you can do to fix this, have a look at https://support.solarwinds.com/SuccessCenter/s/article/Changing-the-server-name-now-results-to-multiple-primary-pollers?language=en_US

bhumphrey

Ah, that makes sense. So the assumption would be, once the tables had the right name, the Configuration Wizard would get the URI value updated to match the new primary polling engine name?

bhumphrey

Hey Tony,

I ended up learning that I was doing this wrong. SQL doesn't take regex like I was expecting. The appropriate way would have been something like:

[C-Z]:\%

Going back to SWQL for this.