4 ms·

For those interested, you can also take a look at our open-source project DeepFlow - https://deepflow.io https://deepflow.io - https://github.com/deepflowio/dee

For those interested, you can also take a look at our open-source project DeepFlow - https://deepflow.io https://deepflow.io - https://github.com/deepflowio/deepflow https://github.com/deepflowio/deepflow We use eBPF to achieve non-intrusive (we call it `zero-code`) observability without modifying any application code, and have implemented three core features: Universal Map, Distributed Tracing, and Continuous Profiling. Yes, we have implemented *Distributed* tracing using eBPF. Because of this achievement, we have also published a paper in ACM SIGCOMM 2023.

intelVISA 3y ago
The copy is way too buzzword dense imo
phrotoma 3y ago
For distributed tracing, how is deepflow able to correlate an inbound request (eg. client call) with an outbound request (eg. 3rd party API call required to service client call) without being inside the business logic?
- sharangxy 3y ago
  Our paper provides some explanations: https://dl.acm.org/doi/10.1145/3603269.3604823 https://dl.acm.org/doi/10.1145/3603269.3604823
  - phrotoma 3y ago
    For the curious, the relevant section is 3.3 and the tl;dr appears to be: "heuristics".
sofixa 3y ago
I have to say I find projects that talk about generic concepts (observability, tracing, eBPF), but then when you dig in the docs it's 100% Kubernetes-specific, to be highly misleading. Not everyone uses Kubernetes, and distributed tracing is a good thing to have regardless of the underlying platform.
- phillipcarter 3y ago
  Another variant of this is when something mentions code profiling and it only supports Go.
- marwis 3y ago
  "Cloud Native" == Kubernetes As in https://www.cncf.io/ https://www.cncf.io/
  - sofixa 3y ago
    Yeah, no. Cloud-native used to mean something even before Kubernetes became mainstream, and technically the CNCF isn't about Kubernetes only, which is why KubeCon and CloudNativeCon are separate events (held together, but separate). Just going to their website shows me two case studies, one is around Kubernetes (Spotify), the other around Vitess (Slack) and has nothing to do with k8s.
    - marwis 3y ago
      Kubernetes heavily dominates there though. I don't recall people throwing Cloud Native as a term before k8s or outside that space. Google trends seems to confirm they emerged at the same time: https://trends.google.com/trends/explore?date=all&q=Cloud%20Native,Kubernetes&hl=en https://trends.google.com/trends/explore?date=all&q=Cloud%20...
      - sofixa 3y ago
        If you remove Kubernetes which is way more popular and hiding the numbers of cloud-native, you'll see that cloud-native started being talked about around 2011, with steady small growth untill it explodes alongside Kubernetes later on. I recall hearing cloud native compared to lift and shift regarding migrating to AWS ~2012-2013.

intelVISA 3y ago

The copy is way too buzzword dense imo

phrotoma 3y ago

For distributed tracing, how is deepflow able to correlate an inbound request (eg. client call) with an outbound request (eg. 3rd party API call required to service client call) without being inside the business logic?

sharangxy 3y ago
Our paper provides some explanations: https://dl.acm.org/doi/10.1145/3603269.3604823 https://dl.acm.org/doi/10.1145/3603269.3604823
- phrotoma 3y ago
  For the curious, the relevant section is 3.3 and the tl;dr appears to be: "heuristics".

sofixa 3y ago

I have to say I find projects that talk about generic concepts (observability, tracing, eBPF), but then when you dig in the docs it's 100% Kubernetes-specific, to be highly misleading. Not everyone uses Kubernetes, and distributed tracing is a good thing to have regardless of the underlying platform.

phillipcarter 3y ago
Another variant of this is when something mentions code profiling and it only supports Go.
marwis 3y ago
"Cloud Native" == Kubernetes As in https://www.cncf.io/ https://www.cncf.io/
- sofixa 3y ago
  Yeah, no. Cloud-native used to mean something even before Kubernetes became mainstream, and technically the CNCF isn't about Kubernetes only, which is why KubeCon and CloudNativeCon are separate events (held together, but separate). Just going to their website shows me two case studies, one is around Kubernetes (Spotify), the other around Vitess (Slack) and has nothing to do with k8s.
  - marwis 3y ago
    Kubernetes heavily dominates there though. I don't recall people throwing Cloud Native as a term before k8s or outside that space. Google trends seems to confirm they emerged at the same time: https://trends.google.com/trends/explore?date=all&q=Cloud%20Native,Kubernetes&hl=en https://trends.google.com/trends/explore?date=all&q=Cloud%20...
    - sofixa 3y ago
      If you remove Kubernetes which is way more popular and hiding the numbers of cloud-native, you'll see that cloud-native started being talked about around 2011, with steady small growth untill it explodes alongside Kubernetes later on. I recall hearing cloud native compared to lift and shift regarding migrating to AWS ~2012-2013.