VictoriaMetrics/VictoriaTraces

Fast and easy to use database for traces, which can efficiently handle terabytes of trace spans.

Owned by VictoriaMetrics

View on GitHub ↗Jump to charts ↓Open shareable report →

VictoriaMetrics/VictoriaTraces has 450+ stars and 50+ forks on GitHub, is written in TypeScript, and was last pushed on Oct 16, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 6 minutes ago
Added to GitGenius on October 12th, 2026
Created on July 7th, 2025
Open Issues & Pull Requests: 68 (+0)
GitHub issues: Enabled
Number of forks: 51
Total Stargazers: 497 (+0)
Total Subscribers: 7 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 15.4 hours
Mean response time: 18.9 days
90th percentile: 48.0 days
Tracked items: 91

Maintainer activity

5 people did triage or write work on this repository in the last 12 months.

Counts unlabeled, assigned, unassigned, milestoned, demilestoned, locked, unlocked over the last 12 months. These are issue and pull request events that require triage or write permission. Commits and code review are not counted. labeled and renamed are excluded because GitHub issue forms record the issue author as the actor. Figures from October 18, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits. How this is counted.

How this project is maintained

About 17% of issues opened in the past year have never received a reply. 86% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Only 51% of issues opened in the past year have been closed. Three people close 94% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 43
New in 7 days: 3
Closed in 7 days: 1
Avg open age: 158 days
Stale 30+ days: 23
Stale 90+ days: 15

Recent activity

Opened in 7 days: 3
Closed in 7 days: 1
Comments in 7 days: 3
Events in 7 days: 22

Top labels

  • enhancement (49)
  • bug (24)
  • question (23)
  • waiting for release (10)
  • documentation (9)
  • vtselect (8)
  • vtinsert (6)
  • good first issue (4)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

VictoriaTraces is a database for distributed traces designed to efficiently handle terabytes of trace spans with fast query performance and straightforward operation.

The tool addresses the challenge of storing and querying large volumes of trace data by providing a purpose-built database optimized for trace workloads. It offers both single-node and cluster deployment options, allowing users to scale from small deployments to large distributed systems. The project is distributed as open source software available through binary releases, Docker images, and source code.

Organizations evaluating VictoriaTraces should be aware that the project is in active development and has not yet reached a stable release. The README explicitly notes that on-disk data structures and API endpoints may change without backward compatibility guarantees. This means early adopters should be prepared for potential breaking changes during upgrades. The tool is suitable for teams that need to ingest and query trace data at scale and can tolerate the instability inherent in pre-release software. Both deployment variants are free to use.

Development activity shows ongoing work to stabilize the codebase and address known issues. The project maintains active communication channels including Slack, social media, and community forums where users can report problems and ask questions. The team has published documentation covering deployment options and upgrade procedures, indicating attention to operational concerns even during the development phase.