VictoriaMetrics/VictoriaLogs

Fast and easy to use database for logs, which can efficiently handle terabytes of logs

Owned by VictoriaMetrics

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

VictoriaMetrics/VictoriaLogs has 2k+ stars and 200+ forks on GitHub, is written in Go, and was last pushed on Oct 17, 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 6th, 2025
Open Issues & Pull Requests: 310 (+0)
GitHub issues: Enabled
Number of forks: 200
Total Stargazers: 2,385 (+0)
Total Subscribers: 16 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 8.7 hours
Mean response time: 18.7 days
90th percentile: 27.7 days
Tracked items: 1,058

Maintainer activity

19 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 8% of issues opened in the past year have never received a reply. 56% of open issues come from outside the core team, a mix of external reports and the maintainers' own roadmap. Work labelled "web-ui" is answered fastest, typically in about 2 hours, while "enterprise" waits about 6 days. 55% of tracked open issues have had no activity in three months. 66% of issues opened in the past year have been closed, leaving a working backlog.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 217
New in 7 days: 7
Closed in 7 days: 2
Avg open age: 220 days
Stale 30+ days: 170
Stale 90+ days: 114

Recent activity

Opened in 7 days: 7
Closed in 7 days: 2
Comments in 7 days: 6
Events in 7 days: 42

Top labels

  • enhancement (548)
  • bug (357)
  • question (201)
  • web-ui (178)
  • logsql (78)
  • vlagent (39)
  • documentation (19)
  • enterprise (13)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

VictoriaLogs is a high-performance log database that handles terabytes of logs with minimal configuration and no predefined schema.

The tool addresses the challenge of efficiently storing and querying large volumes of log data. It operates as a schema-free database, meaning logs can be ingested without defining field structures in advance. The system scales both vertically on single nodes and horizontally across clusters, adapting to deployments ranging from small setups to large-scale operations processing terabytes daily. Both single-node and cluster versions are open source and free to use.

Teams should consider VictoriaLogs if they need a lightweight, zero-config alternative to traditional log management systems. It suits organizations looking to avoid complex schema management while maintaining high performance at scale. The project provides multiple query interfaces, including a built-in web UI, Grafana integration, and converters that translate SQL and LogQL queries to its native LogsQL format, making it accessible to users familiar with other logging platforms. Deployment options include binary releases, Docker images, and both single-node and cluster configurations, allowing flexibility in how it fits into existing infrastructure.

Development activity shows consistent engagement with the project. The team maintains comprehensive documentation covering deployment types, upgrades, and usage patterns. Community channels span multiple platforms including Slack, social media, and messaging services, indicating active user support. The project publishes a changelog and provides clear upgrade guidance, suggesting regular maintenance and evolution of the codebase.