Viewing profile — sharangxy

You can also check out DeepFlow [1], where we implemented distributed tracing for microservices using eBPF, which of course also includes observability of K8s networks. 1. https://…

DeepFlow [1][2] is one of them, where we implemented distributed tracing for microservices using eBPF. 1. https://deepflow.io 2. https://github.com/deepflowio/deepflow

We have implemented zero-code distributed tracing with eBPF. https://github.com/deepflowio/deepflow

The biggest difference: DeepFlow enables *Distributed* Tracing. In addition, DeepFlow combines the capabilities of eBPF and cBPF to achieve full-stack tracing of syscall + network_…

I believe the current situation is like this. The advantage of eBPF lies in *request granularity* (i.e. PRC, API, SQL, etc ...) distributed tracing. To trace the internal functions…

Some of our users’ ancestral processes are running on kernel 2.6, and the operations staff dare not upgrade the kernel. Indeed, there are many limitations in 2.6, but the simple tr…

We are in the process of translating more documents into English, and we also greatly welcome the help of the community!

VP of DeepFlow here. Thank you for your interest in DeepFlow! Yes, we have implemented distributed tracing using eBPF. In simple terms, we use thread-id, coroutine-id, and tcp-seq …

Our paper provides some explanations: https://dl.acm.org/doi/10.1145/3603269.3604823

For those interested, you can also take a look at our open-source project DeepFlow. [1] https://deepflow.io [2] https://github.com/deepflowio/deepflow We use eBPF to achieve non-in…

For those interested, you can also take a look at our open-source project DeepFlow - https://deepflow.io - https://github.com/deepflowio/deepflow We use eBPF to achieve non-intrusi…

Troubleshooting Your Microservices in Zero Code