What is "Background threads" and why all PurePath are broken

[imoskovko1]

Hello!

Can you explain what is "Background threads" and why all PurePath are broken?

Pic:

Regards,

Igor

[JamesKitson]

Background activity services are described here: https://www.dynatrace.com/support/help/shortlink/s...

Couldn't tell from a screenshot why you'd be having capture errors, see if there's any more details there and consider checking with support.

[imoskovko1]

Frankly i red it and do not understand diff between foreground thread and background one. Would you be so kind to explain.

[JamesKitson · Accepted solution]

This msdn post explains it pretty well: https://docs.microsoft.com/en-us/dotnet/standard/threading/foreground-and-background-threads

[imoskovko1]

Kind thanks!

[imoskovko1]

Thank you James. After discussing it with our developers i understud. Do you know why all PurePaths for background thread are captured with error?

[JamesKitson]

No, can't determine that from a screenshot. I would reach out to Dynatrace ONE or support if drilling into that PurePath doesn't reveal anything more.

[rodrigo_alvare1 · Accepted solution]

Hello Igor,

What you are sing there are corrupted purepahts on the process detected as "background process". Corrupted Purepaths can have different reasons, like:

• Network issues, e.g. data from at least one agent does not arrive on the cluster
• Complexity issues, e.g. too many request attributes or custom service calls captured or timed-out requests

The Purepaths will show everything Oneagent grabbed so you look into what failed.

If it was a call out to some public resource that took too long or a call out to a host/process that was particularly burdened at the time. If you know what process is behind the purepath at the point of corruption, then you might be able to see explanations in the logs about why the subpath was dropped or lead to corruption of the larger path.

Regards