we have this common concern raised by Application teams to see thread dump and memory dump of a past duration when some issue occurred in the application for analysis.
And because it is not possible to reproduce the issue again (when we can run thread/memory dumps live) , we remain devoid of what happened at that time of the issue..
Also it is not possible to let thread /memory dumps run forever for every application as we have a huge environment..
Please share if anybody has faced similar issue and got some workaround to deal with this.
Answer by Babar Q. ·
Hello @Himanshu M.
Enables/disables automatic generation of a Leak Analysis Memory Snapshot is already available which they can pre-process on demand (Total Memory & Session Browser dashlets).
You might trigger thread dumps at times when the load on the system under diagnosis is low, to ensure that there are no threads leaking, or to compare the CPU usage of different threads to previously created thread dumps.
Dynatrace Log4net log from MongoDB 3 Answers