deepflowio/deepflow

eBPF Observability - Distributed Tracing and Profiling

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 5 minutes ago
Added to GitGenius on September 16th, 2026
Created on January 16th, 2022
Open Issues & Pull Requests: 271 (+0)
GitHub issues: Enabled
Number of forks: 484
Total Stargazers: 4,276 (+1)
Total Subscribers: 51 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 28.6 hours
Mean response time: 9.5 days
90th percentile: 14.6 days
Tracked items: 191

Most active contributors

Sign in to see contributor activity.

How this project is maintained

99% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Three people close 57% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 81
New in 7 days: 2
Closed in 7 days: 0
Avg open age: 487 days
Stale 30+ days: 73
Stale 90+ days: 68

Recent activity

Opened in 7 days: 2
Closed in 7 days: 0
Comments in 7 days: 1
Events in 7 days: 1

Top labels

  • bug (127)
  • feature (48)
  • help wanted (2)

Detailed Description

DeepFlow is an eBPF-based observability platform that provides distributed tracing and profiling without requiring code instrumentation.

The platform addresses the challenge of gaining visibility into complex distributed systems by leveraging eBPF to automatically capture network traffic, system calls, and application behavior at the kernel level. This approach eliminates the need to modify application code or add manual instrumentation, making it particularly valuable for environments where instrumentation is impractical or where legacy systems cannot be easily modified. The tool collects telemetry data across containerized and Kubernetes environments, supporting integration with OpenTelemetry and providing both distributed tracing and continuous profiling capabilities.

DeepFlow suits organizations running complex microservices architectures, particularly those with GPU workloads, Kubernetes clusters, or large language model deployments where traditional instrumentation approaches are cumbersome. The zero-code instrumentation model makes it attractive for teams managing heterogeneous systems where standardizing on instrumentation libraries is difficult. It is designed to work across diverse infrastructure including cloud-native environments, making it applicable to organizations seeking unified observability without widespread code changes.

The project shows active development with regular commits addressing core observability functionality. Work spans multiple technical areas including kernel-level data collection, distributed tracing pipeline implementation, and profiling infrastructure. The codebase demonstrates ongoing refinement of eBPF probe management and telemetry processing systems. Development activity indicates sustained focus on expanding platform capabilities and maintaining compatibility across different deployment scenarios.