Any news about this topic? I would like to underline how much important this feature is in prod envs where we cannot think to trigger them manually: https://community.dynatrace.com/t5/Dynatrace-Open-Q-A/Memory-Dump-for-Memory-Leak-analysis-Best-Prac...
It's also quite important in our company. We don't have Java 11 yet and therefore can't use continuous profiling features yet. Possibility to automatically trigger memory dumps based on certain criteria/thresholds or schedule is a big requirement for us.
Just to notify that, currently we are using the JVM parameter: -XX:+HeapDumpOnOutOfMemoryError
It is the ootb way we can force the JVM to trigger a dump. It would be great if Dynatrace is at least aware of these dump. This way we can use the download feature offered by DT to manage them