OutOfMemoryError
HI all
Before trying and validate it real,...
Using the Java Exception sensor, is the OutOfMemoryError.init() contructor is realy trapped and always added in the current PurePath while the JVM is crashing....
If not is it planned to provide this metric as a standard JVM measure ?
The objective is get a consistent and relevant metrics / stats over this "OutOfMemory" on thousands of JVM, and not only through Incident DashBoards...
Thanks a lot
Philippe
I'm not sure what you want to achieve but are you looking to get a PP if the JVM goes out of memory? If so you probably want to investigate of placing a entry point sensor on the mentioned method.
Why is the incident that is beeing triggered on a OOM of a JVM (based on standard JVM functionality) not good enough?
Thanks for your response / question Reinhard 
Yes...
Because or Customer has thousands of JVM and the Incident View is not Enough to have a synthetic Top 10 of JVM have triggered OOM within a period.
So I need this kind of Metric as a real Measure to use DashBoarding capabilities.
I've checked with DT6 and unfortunately The OOM could not be catch by instrumentation.
Because Dynatrace could intercept the OOM it could add a dedicated measure for this case.
If you have better ideas I'll be interested.
Thanks
Philippe
EMEA Community Member of the Month - November 2018
Announcing Dynatrace's EMEA Community Member of the Month for November 2018, Mathieu C.! Click here to read more! LATAM Community Member of the Month - November 2018
Announcing Dynatrace's LATAM Community Member of the Month for November 2018, Rene S.! Click here to read more! 