Hello,
configured IIS application process on DynaTrace 5.6 collects PurePaths OK.
Application pool is recycled each hour by scheduler. After automatic restart sometimes is created new process in Monitored process list and sometimes is new process joined to previous one see Process list image. Detail of joined processes is on Process detail image, where can you see different PID.
Correct is joining into one process I think.
What causes process multiplication? How can I prevent this behavior?
Thank you for any advice.
Antonin
Answer by Lopes D. ·
It could be that the CLR goes offline and then online too fast, the Collector doesn't register it as offline when the new one is already connecting.
There is an option on the dtcollector.ini you can use to disable this behavior and group agents with the same name.
-Dcom.dynatrace.diagnostics.collector.agentcenter.unique_agent_names_with_index=
false
Answer by Paul D. ·
app pool recycling causes new application to be created and all threads start running in this new process with a new process id. The old threads age out of the old app pool process (w3wp,exe) and it goes away so yes you may have two w3wp processes handling the same app pool after a recycle until the old threads age out.
Learn how Dynatrace Real User Monitoring automatically detects errors that impact your end users caused by erroneous 3rd party or CDNs.
December 12, 4:00 pm CET / 10:00 am ET
Register here
Learn how Dynatrace Real User Monitoring automatically detects errors that impact your end users caused by erroneous 3rd party or CDNs.
December 12, 4:00 pm CET / 10:00 am ET
Register here
Learn how Dynatrace Real User Monitoring automatically detects errors that impact your end users caused by erroneous 3rd party or CDNs.
December 12, 4:00 pm CET / 10:00 am ET
Register here
Learn how Dynatrace Real User Monitoring automatically detects errors that impact your end users caused by erroneous 3rd party or CDNs.
December 12, 4:00 pm CET / 10:00 am ET
Register here