To many components

jamiewillis

So it seems our polling server has way too many components, support says 8-10K at most and we are on 21k !!!

As part of the cleanup process and  to get a lean mean monitoring machine, I would like to export a list of all devices monitored, and preferably all devices monitored with everything that is monitored on them

How would I do this?

Thanks in advance!

mesverrum

While it is good to get rid of monitors that you don't need and especially good to remove any of them that are not configured correctly, I will tell you that 10k limit is a bit of a cop out/red herring.  In MANY cases the first line support doesn't seem to understand the nuance of the loads and are just spitting back a spec appears to be wildly out of date ever since the Appinsight templates came out.  If you are using the Appinsight templates they create a very high number of components (usually something around 100-1000 components each time you assign one), but because they gather their data via parsing scripted results they don't have anywhere near the same overhead as what you would get from running 20k individual components with their own separate requests and processing one by one.  The most legitimate way to actually know if you are actually overloading your SAM monitors is just to check the SAM Load % on the polling engines page under settings.  If a support tech is trying to tell you that your SAM is overloaded but the load you see there is under 70% then they are probably sending you down a rabbit hole.

The simplest way to get a count of what's out there is to use a custom SWQL report with something like this

select n.caption, count(n.Applications.Components.name) as [Components]

from orion.nodes n

where n.Applications.ApplicationID is not null

group by n.caption

In reality you may need to do something a bit more elegant like this to get a more accurate sense of what is happening.  I haven't done the testing to get a sense of how much any given appinsight component compares in terms of real load, but I can assure you a single server of the IIS template will usually create ~100 components and it will have nearly none of the impact on the sam polling load compared to me building out all those same components one by one in a traditional template.  From past experience it feels like maybe the equivalent of 5-10 components per instance of appinsight (complicated by the number of websites on your server, or the number of databases in your SQL, etc)

select n.caption, comp.components as [Traditional Components], app.apps as [AppInsight Templates Assigned], app.components as [AppInsight Components]

from orion.nodes n

left join (select count(*) as Components, com.application.nodeid

from orion.apm.Component com

where com.Application.Template.Name not like '%appinsight%' and com.Disabled=0

group by com.application.nodeid

) comp on comp.nodeid=n.nodeid

left join (select count(*) as Components, com.application.nodeid, count(distinct com.Application.ApplicationID) as Apps

from orion.apm.Component com

where com.Application.Template.Name like '%appinsight%' and com.Disabled=0

group by com.application.nodeid

) app on app.nodeid=n.nodeid

where (comp.components is not null or app.apps is not null)