Count of all the "things" solarwinds is monitoring and their respective status

Hello,

I am putting together KPI metrics of the use of Solarwinds and an item I'd like to pull out is the count and status of ALL the things Solarwinds is checking. This would include components (SAM items), API pollers, SNMP devices (port status, hardware status), DPA, etc.

We've been able to pull a count of components but I don't think it includes items from NPM, VIM, NCM, etc.

Ultimately, the count of this should go up week over week as we continue to create components, add devices etc. For status, we'd want it to go down with tuning exercises.

Any thoughts?

Find more posts tagged with

Component

apm

npm

report

Accepted answers

All comments

adam.beedell

You want the count of Elements not components (see settings -> polling engines or something like that)

This would be a really big query, it'd probably be like SELECT COUNT STATUS FROM X GROUP BY STATUS UNION ALL repeat for every table you care about

Maybe run it like once a day overnight or something unless you need to do more

mrt3385

thanks. what tables would i start from?

adam.beedell

In some other tools this would be closer to like SELECT STATUS FROM THINGS, in solarwinds this is more complicated, just a tradeoff. It depends what you care about really. If there's like UDT in your environment in a big way you'd want to add some port stuff. Maybe Compliance or somethat that isnt really a status.

In a generic environment I'd take something like this if I was trying to show EVERYTHNG:

Nodes

Volumes

Interfaces

VMs

Hosts (+Virtual Datacenters, Virtual Clusters, maybe some other bits if those are important)

Applications

Components (Could do multi-value sub-components?)

Transactions

Groups

Hardware sensors maybe?

IP Operations?

Something like that

SteveK

To build off of this, when you go for components make sure you excluded disabled components. Depending on the environment and amount of Appinsight you are using, that number could get extremely stupid.

mesverrum

Really i think this would mostly just end up being a bunch of sam sql components doing select count(*) from solarwindsorion.dbo.<tablename>

Just have to identify all the relevant tables for things you are building. You are totally correct that looking at components and elements isn't complete because those are really only counting things solarwinds has traditionally used for billing purposes. UNDP, Hardware health sensors, VIM objects, SRM objects, etc etc etc, there is a ton of stuff that you might want to capture and track if you want to report on how usage is growing or shrinking or whatever.