AppInsight for SQL and APE Limitations

monitoringlife

Hello,

I have a large environment with a lot of IIS and SQL servers.  I currently have 170 'AppInsight for SQL' setup.  I know from the 'Scalability Engine Guidelines for SolarWinds products' that an APE should try to stay around 10,000 components.  AppInsight for SQL takes up at least 50 for each instance.  I have an APE that is significantly over this limit but appears to be keeping up with its workload.

Anyone else in a large environment that can offer advice?

serena

monitoringlife  wrote: Hello, I have a large environment with a lot of IIS and SQL servers.  I currently have 170 'AppInsight for SQL' setup.  I know from the 'Scalability Engine Guidelines for SolarWinds products' that an APE should try to stay around 10,000 components.  AppInsight for SQL takes up at least 50 for each instance.  I have an APE that is significantly over this limit but appears to be keeping up with its workload. Anyone else in a large environment that can offer advice?

Hi,

The scalability engines guidelines are there to help customers stay within the traditional bounds of what we've seen for SAM customers, however there have definitely been customers who have had well running SAM installations with above that number. The factors that come into play are: what kind of component monitors are you running? Are they running efficient scripts? are they doing heavy duty parsing? If that's the case, that can change the polling weight equation for your environment. We are currently working on increasing our scalability for components, so I would love more information from you on what you feel the sweet spot is for your monitoring environment. Is it 20000 components per ape? 30000? More?