.Net Thread Tagging sensor creating many .ctor nodes in purepaths
Hi,
We are seeing high purepath size due to nodes created by the .Net Thread Tagging sensor. When we place the sensor we wee many .ctor nodes in the purepaths.
Here is a screenshot of one purepath that shows the .ctor nodes.
The Class of the method is System.Threading.Tasks.Task
We need Thread tagging for the complete tracing of the request across threads.
My question can the sensor be updated to exclude this method capture and still get the thread tagging? or is this method need for tagging.
-Sreerag
The issue we see is in v5.0.0 .
We i checked he sensor pack i could find that the v5.0.0 sensor pack has the sensor for method System.Threading.Tasks.Task.ctor() .
Where as the v5.6.0 doesn't have this method in the sensor pack.
We are upgrading our v5.0.0 next week and will watch to see if things are ok.
-Sreerag
hi Sreerag,
we improved this in dynaTrace 5.5 and are using another method for .NET Tasks (ScheduleAndStart()) since then.
so after the upgrade these nodes will be gone.
best, Christian
Welcome the
Dynatrace Community Forums
Check out the Forum User Guide and Forum Guidelines to learn how to get started.Community Member of the Month
August 2017
Announcing Dynatrace's Community Member of the Month for August 2017, Rick B.! Click here to read more! 
