Exception Sensor Questions
Recently we have been noticing that we are seeing exceptions in our log files (and in the Logging and in the Errors Dashlets) but those exceptions aren't appearing in the Exceptions Dashlet of Dynatrace. A little further research showed the reason…
The exception we aren't seeing is a java.lang.NullPointerException. It looks like Dynatrace is setting up the Exceptions Sensor to exclude java., javax. and sun. by default. I realize that in order for me to capture our NullPointers that I need to remove the java. exclusion but I wanted to ask first… What kind of an impact will (may) this have on the performance of our applications? I'm assuming that Dynatrace excluded it for a reason. I'm hoping someone on this forum can help me understand why.
Thanks in advance.
Frank
Hi Frank
The "impact" is that there is more data captured by dynaTrace. Your PurePaths will get longer and that means that fewer PurePaths can fit in the in-memory live session of the dT Server. Now - that might not be a problem for you at all. Best is to change your configuration and see how many additional exceptions you capture and how that impacts the PurePath size. The exception sensor also has an "overhead protection" setting - this will prevent dynaTrace having too much overhead because we wont capture all stack trace details for all captured exceptions.
Long story short: give it a try. Look at the capture exceptions and exclude those that you dont need.
As always... Good advice. And good information knowing that there's an overhead protection.
Thanks Andreas!
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
September 2017
Announcing Dynatrace's Community Member of the Month for September 2017, Tarun A.! Click here to read more! 