Answers for "Multiple Thresholded Excetions?"https://answers.dynatrace.com/questions/106733/multiple-thresholded-excetions.html
The latest answers for the question "Multiple Thresholded Excetions?"Answer by Andreas Grabnerhttps://answers.dynatrace.com/answers/106734/view.html
<p>Hi</p><p>Dynatrace will capture a lot of exceptions as configured in your Exception Sensor. By default we aggregate the same exception type so that in the PurePath we show you that you had e.g: 300 Exceptions of that type and 100 of a different type in case you have more than 3 isntances of these exception types per PurePath underneath an instrumented method node.</p><p>So - for the first 3 exceptions of any type dynatrace will TRY to capture full details including full stack trace. For the rest it will just count the instances but will not capture stack traces. I said TRY as we also have a Stack Trace Capturing Limit. If you check out the configuration of your Exception Sensor in your System Profile you can see how many stack traces we capture per second. Default is 16. Thats why most of your exceptions - especially if your app is in a mode where it throws a lot of them - will not show stack trace information. And - for those exceptions that are thrown more than 3 times per purepath we also only capture the class but not the detailed messages for each instance</p><p>This is the reason why you see this type of data.&nbsp;</p><p><span style="line-height: 1.4285715;">If you want to see more details then you could increase the capture limits (&gt; 16 per second) or even for a short period of time turn off Exception Aggregation in the sensor prpoerties. I say &quot;short period&quot; because we built this feature to capture exception count but not all the details as it is typically not necessary to have all stack traces and it also means some overhead that we add</span></p><p>I hope this explanation makes sense</p><p>Andi</p>Thu, 23 Jul 2015 17:45:27 GMTAndreas Grabner