Purepath capture error ?

MAkimov — Thu, 06 Jul 2023 13:50:46 GMT

Hello

I have a microservice (Kubernetes)

Process technology - .NET (.NET Core 2.2.2), ASP.NET Core (2.2.0.18316), ASP.NET Core SignalR (1.1.0.18316), and CLR (CoreCLR 4.0.30319.0)

The developers said they noticed a strange job in the service.

it reboots by itself

In PurePath I see - Purepath capture error

Some data could not be collected or transmitted. This is most likely due to a resource congestion on network, host or process level (S11)

That does this mean?

Exception within PP

The Socket transport's send loop completed gracefully.

After this, the service restarts itself.

Is it possible that due to the work of agents, the service can be restarted independently?

Re: Purepath capture error ?

rodrigo_alvare1 — Thu, 18 Apr 2019 13:19:24 GMT

Hello, Mikhail,

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.

In your case the exception shows that the connection was closed/killed, so that probably is the reason, the Purepath shows as corrupted.

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

topic Purepath capture error ? in Container platforms

Purepath capture error ?

Re: Purepath capture error ?