Continuous thread analysis vs. Manual thread dump analysis

[Babar_Qayyum]

Dear All,

Can we take the on-demand thread dumps?

Can we schedule the thread dumps?

What is the overhead and drawbacks of the continuous thread analysis feature?

Regards,

Babar

[davide_diana1]

I take advantage of this to ask - What is the retaining period of the continuous thread analysis? Is it related to the code-level retaining period? (Purepath)

[dnpmoris]

I am also looking for thread dump creations. looking for update

[josef_schiessl]

Hi, see my reply below! 

[josef_schiessl]

Hi everyone,

Heres some answers to these old but still relevant questions:

Overhead of continous thread analysis is minimal and the OneAgent itself tracks overhead and will automatically adjust capture rate of thread samples.

Data retention is the same as Distributed Trace Data (https://www.dynatrace.com/support/help/shortlink/data-retention#purepath). 

There is no way in Dynatrace to trigger a thread dump, also no need for it since with continous thread analysis the OneAgent captures thread dumps all the time automatically.

[Babar_Qayyum]

Hello @josef_schiessl 

There are a few requirements to get the continuous thread analysis benefits. It is not applicable to all environments. So whether Dynatrace will have to change the minimum requirements or they will have to introduce the manual way.

Regards,

Babar 

[josef_schiessl]

True, if there is a need for the ability to trigger thread dumps via OneAgent, I would suggest to create an RFE in the Product Ideas section!