Hey everyone,
So I wanted to start a conversation about SAM and component count. Has anyone else received inconsistent responses from SolarWinds regarding overall component count. I know on the legacy/traditional licensing model they say an APE can handle 10k components and 40k when it comes to HCO. I've had talks with engineers in the past that they claim the component count is really a best practice but it ultimately comes down to the overall weight/demand that a specific component monitor uses. Of course when asking how to calculate the weight of an assigned monitor, there really isn't a way to do that (if you have a good way, I'm all ears).
Essentially the catalyst for this conversation revolves around the component count in my own environment. We have several APEs and had a single poller over 40k and us runnig on the non-subscription license. When I ran some queries in the environment, the main consistancy is the bloat of components that Appinsight generated. We actually had a single IIS server ding us for 24k components. Our top 15 monitors (either Appinsight for IIS and Appinsight for SQL) equated to about 60% of all components in the environment. Really Appinsight collectively make up over 90% of all components in my environment. I've also been told in the past that Appinsight monitors are kind of a different beast alltogether and to take their component counts with a grain of salt. That those monitors are more efficient than other SAM components and that the count of components from Appinsight take alot less resources to poll. Which then the high count comes back and dings us during other support calls or the general health checks.
So whats been your experience in this area?
