cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

This product reached the end of support date on March 31, 2021.

Dynatrace limit on maximum dotNet agent configurations?

emeck
Contributor

In the dynatrace powershell module on github, this bit of code appears:

while (Test-Path ($regPath+"\"+($index -as [string])))
{
$index++
if ($index -gt 15)
{
"Too many processes to instrument (15 processes already exceeded)."
return
}
}

Is there a recommended limit within the dynatrace agent where a specific number of dotnet processes should not be exceeded when instrumenting on a windows server? With the latest Windows 2012 IIS 8, Microsoft has recommended against shared application pools and running each app in it's own pool. On some of our servers, that could mean several hundred application pools. Any feedback on this?

2 REPLIES 2

patrick_thurner
Dynatrace Pro
Dynatrace Pro

Hi Erich,

there's no dedicated limit, but practically there will be limits due to possible TCP connections between agents and collectors.

The most important thing on thing you have to care is the maximum numbers of agents per collector: https://community.dynatrace.com/community/display/...

This hard-deck in the script of max 15 already existing configuration entries could be removed and is just a prevention not blowing up the registry by adding regularly new processes - which, of course, is not suitable for e.g. large hosting environments as you mentioned.

The easiest way if you want every apppool instrumented, is to white-list just "w3wp.exe" without further command line parameters.

Sounds good, especially since by admission we've already blown that limit entirely. Thanks!!