PurePath availability resiliency in Cluster failure condition

[poshea]

We have had a Managed cluster node fail and need to be pulled from the cluster, and when this happened the PurePaths stored on this cluster node are no longer available (though new continue to be stored once agents reconnect). Is there any way anyone has found, or anything on the roadmap, to ensure availability of these PPs in a failure condition so users are not impacted?

[Radoslaw_Szulgo · Accepted solution]

Raw transaction data (call stacks, database statements, code-level visibility, etc.) isn't replicated across nodes, it's evenly distributed across all nodes. As a result, in the event of a node failure, Dynatrace can accurately estimate the missing data. This is possible because this data is typically short lived, and the high volume of raw data that Dynatrace collects ensures that each node still has a large enough data set even if a node isn't available for some time.

https://www.dynatrace.com/support/help/setup-and-configuration/dynatrace-managed/basic-concepts/dyna...