GreptimeTeam/greptimedb

The open-source observability database. One columnar engine for metrics, logs, and traces, on object storage.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 2 minutes ago
Added to GitGenius on September 9th, 2026
Created on April 11th, 2022
Open Issues & Pull Requests: 264 (+0)
GitHub issues: Enabled
Number of forks: 540
Total Stargazers: 6,662 (+0)
Total Subscribers: 57 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Issue API getrepoissuespagesummary failed: 429 Rate limit exceeded. Please try again later.

Detailed Description

GreptimeDB is a columnar observability database that unifies metrics, logs, and traces in a single engine running on object storage.

The tool addresses the operational complexity of running separate specialized systems for different observability signals. Rather than maintaining distinct databases for metrics, logs, and traces, GreptimeDB consolidates these workloads into one columnar engine. This unified approach reduces infrastructure overhead while leveraging object storage for cost-effective, scalable persistence. The database supports standard observability protocols and query languages, including PromQL for metrics queries and OpenTelemetry data ingestion, making it compatible with existing observability workflows.

Teams should consider GreptimeDB if they want to simplify their observability stack by consolidating multiple signal types without running separate specialized systems. It suits cloud-native deployments and self-hosted environments where reducing operational complexity matters. The project is particularly relevant for scenarios involving high-cardinality data and wide-event schemas. Organizations evaluating adoption should note that the core is open-source and the tool is designed for distributed deployment across your own infrastructure rather than as a managed service.

The project maintains multiple release channels including stable builds for production use, canary releases for pre-release testing, and nightly snapshots. Development activity shows consistent integration testing coverage and regular release cycles across these channels. The team publishes a public roadmap documenting planned work.