odigos-io/odigos

Distributed tracing without code changes. 🚀 Instantly monitor any application using OpenTelemetry and eBPF

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 18 minutes ago
Added to GitGenius on September 18th, 2026
Created on June 8th, 2022
Open Issues & Pull Requests: 166 (+0)
GitHub issues: Enabled
Number of forks: 257
Total Stargazers: 3,679 (+0)
Total Subscribers: 30 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 3.1 days
Mean response time: 58.5 days
90th percentile: 269.8 days
Tracked items: 27

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 1
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 42 days
Stale 30+ days: 1
Stale 90+ days: 0

Recent activity

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

Top labels

  • stale (11)
  • bug (7)
  • frontend (3)
  • never-stale (3)
  • good first issue (2)
  • hacktoberfest (2)
  • help wanted (2)
  • enhancement (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Odigos is a distributed tracing solution that instruments applications without code changes using OpenTelemetry and eBPF technology.

The tool addresses the challenge of adding observability to running applications by automatically generating distributed traces without requiring developers to modify source code. It works by leveraging eBPF for high-performance instrumentation across multiple languages, separating data recording from processing to minimize runtime overhead. Applications written in Java, Python, .NET, Node.js, and Go can be instrumented instantly through Odigos, which then exports traces in OpenTelemetry format.

Odigos suits platform engineers, DevOps professionals, and SREs managing Kubernetes environments or virtual machines who need to add tracing capabilities quickly without waiting for application teams to modify their code. It works well for organizations seeking to avoid vendor lock-in, as it integrates with various monitoring backends and generates vendor-neutral OpenTelemetry data. The tool provides opinionated defaults and best practices out-of-the-box, reducing the need for deep OpenTelemetry expertise. For compiled languages like Go, which have historically been difficult to instrument without code changes, Odigos offers a distinctive advantage through its eBPF-based approach.

The project maintains active development with regular releases and demonstrates strong community engagement through its public issue tracking and documentation. The codebase shows consistent updates across its core components and instrumentations for supported languages. Development activity spans multiple areas including the CLI, Kubernetes operator functionality, and language-specific instrumentation modules, indicating sustained work across the full stack rather than focus on a single component.