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...
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
Hello, we are implementing automation which require triggering a memory dump of a pod via API once it has been identified as a problem.
Therefore we are also requiring API access to triggering, viewing, and getting memory dumps.
Please implement this feature.