VictoriaMetrics/VictoriaLogs

Health v2 · maintenance only

Adoption not part of the score

2191 stars · 185 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded

VictoriaLogs is an open-source, schema-free database purpose-built for storing and querying logs, scaling from small setups to terabytes of logs per day. It offers single-node and cluster deployments, LogsQL query language, and integrations with Grafana, OpenTelemetry, and common log shippers like Filebeat, Fluentbit, and Vector.

Use cases

• store and query terabytes of application logs
• replace Elasticsearch or Loki for log management
• centralize Kubernetes container logs
• ingest logs from Filebeat, Fluentbit, Promtail, or OpenTelemetry
• query logs with SQL-like or LogQL-like syntax
• build a self-hosted SIEM log backend
• visualize logs in Grafana dashboards

When to choose

• you need a fast, lightweight, zero-config log database that scales vertically and horizontally
• you want an open-source alternative to Elasticsearch or Loki with lower resource usage
• you already use Grafana or OpenTelemetry and need a logs backend
• you need both single-node simplicity and a cluster option for large-scale deployments

When to avoid

• you need a general-purpose document or relational database rather than a log store
• you require managed SaaS logging with no self-hosting responsibility
• your workload is primarily metrics or traces rather than logs (use VictoriaMetrics or VictoriaTraces instead)

Facets

service · maturity active

database search-engine logging monitoring databases monitoring windows self-hosted go cross-platform log-database logsql elasticsearch-compatible loki-alternative opentelemetry grafana siem observability single-node cluster devops search linux macos docker kubernetes

Member repositories

For agents

markdown · JSON · MCP: product_card(name="VictoriaMetrics/VictoriaLogs")