Can we pull "NodeName" or other Custom Properties directly from the SolarWinds database?

We are configuring a 3rd party CMDB system to import a node list from our SolarWinds Orion database. Currently, it is successfully reading from the NodesData table.

Is it possible to read the "Node Name" property and other Custom Properties directly from the database as well? If so, any tips are appreciated.

Thanks for your assistance in advance.

Kevin

Find more posts tagged with

Accepted answers

simon.stone

Node name is the Caption field in the NodesData table. You can get the custom properties if you read the "Nodes" view.

All comments

simon.stone

Node name is the Caption field in the NodesData table. You can get the custom properties if you read the "Nodes" view.

wluther

@km3000 Just out of curiosity, have you considered using the API to pull data from the Orion DB? I believe there may be a tiny bit more safety rope built into using the API, compared to direct DB access.

km3000

No, the preferred method for this developer is through a SQL connection but if we are unable to get this to work we may go down that road. Thanks for the response.

km3000

This should work for us. I appreciate the information.

kenosmith3

just curious what CMDB are using? Does it rhyme with CircusNow?

marcrobinson

Just an FYI - sql tables may change during any Orion upgrade. This is another reason to use the api/swql - Solarwinds works to maintain them through upgrades. @wluther is correct about the safety features built into swql calls. I have had to quickly fix sql based alerts and reports following a few upgrades. Then I learned my lesson.

HerrDoktor

CircusWOW would probably prefer REST API calls. At least that’s what I have seen in my last projects with this solution

km3000

We are using Cherwell. Sorry for slow response.

dclick

Get a new developer. direct DB access is not only a huge security risk, but as others point out, Solarwinds has a habit of changing table names during upgrades.

simon.stone

I agree with the changing of tables, but why is it a "huge security risk"? Granted if the SQL security is implemented badly by the DBA, but if the account used for access is say a data_reader to a specific set of tables, it poses no more risk than an API does.