Greptimedb

<p align="center"> <picture> <source media="(prefers-color-scheme: light)" srcset="https://cdn.jsdelivr.net/gh/GreptimeTeam/greptimedb@main/docs/logo-text-padding.png"> <source media="(prefers-color-scheme: dark)" srcset="https://cdn.jsdelivr.net/gh/GreptimeTeam/greptimedb@main/docs/logo-text-padding-dark.png"> <img alt="GreptimeDB Logo" src="https://cdn.jsdelivr.net/gh/GreptimeTeam/greptimedb@main/docs/logo-text-padding.png" width="400px"> </picture> </p> <h2 align="center">One database for metrics, logs, and traces<br/> replacing Prometheus, Loki, and Elasticsearch</h2>

The unified OpenTelemetry backend — with SQL + PromQL on object storage.

<div align="center"> <h3 align="center"> <a href="https://docs.greptime.com/user-guide/overview/">User Guide</a> | <a href="https://greptimedb.rs/">API Docs</a> | <a href="https://github.com/GreptimeTeam/greptimedb/issues/7685">Roadmap 2026</a> </h3> <a href="https://github.com/GreptimeTeam/greptimedb/releases/latest"> <img src="https://img.shields.io/github/v/release/GreptimeTeam/greptimedb.svg" alt="Version"/> </a> <a href="https://github.com/GreptimeTeam/greptimedb/releases/latest"> <img src="https://img.shields.io/github/release-date/GreptimeTeam/greptimedb.svg" alt="Releases"/> </a> <a href="https://hub.docker.com/r/greptime/greptimedb/"> <img src="https://img.shields.io/docker/pulls/greptime/greptimedb.svg" alt="Docker Pulls"/> </a> <a href="https://github.com/GreptimeTeam/greptimedb/actions/workflows/develop.yml"> <img src="https://github.com/GreptimeTeam/greptimedb/actions/workflows/develop.yml/badge.svg" alt="GitHub Actions"/> </a> <a href="https://codecov.io/gh/GrepTimeTeam/greptimedb"> <img src="https://codecov.io/gh/GrepTimeTeam/greptimedb/branch/main/graph/badge.svg?token=FITFDI3J3C" alt="Codecov"/> </a> <a href="https://github.com/greptimeTeam/greptimedb/blob/main/LICENSE"> <img src="https://img.shields.io/github/license/greptimeTeam/greptimedb" alt="License"/> </a> <br/> <a href="https://greptime.com/slack"> <img src="https://img.shields.io/badge/slack-GreptimeDB-0abd59?logo=slack&style=for-the-badge" alt="Slack"/> </a> <a href="https://twitter.com/greptime"> <img src="https://img.shields.io/badge/twitter-follow_us-1d9bf0.svg?style=for-the-badge" alt="Twitter"/> </a> <a href="https://www.linkedin.com/company/greptime/"> <img src="https://img.shields.io/badge/linkedin-connect_with_us-0a66c2.svg?style=for-the-badge" alt="LinkedIn"/> </a> </div>

• Introduction
• ⭐ Key Features
• How GreptimeDB Compares
• Architecture
• Try GreptimeDB
• Getting Started
• Build From Source
• Tools & Extensions
• Project Status
• Community
• License
• Commercial Support
• Contributing
• Acknowledgement

Introduction

GreptimeDB is an open-source observability database built for Observability 2.0 — treating metrics, logs, and traces as one unified data model (wide events) instead of three separate pillars.

Use it as the single OpenTelemetry backend — replacing Prometheus, Loki, and Elasticsearch with one database built on object storage. Query with SQL and PromQL, scale without pain, cut costs up to 50x.

Features

| Feature | Description | | --------- | ----------- | | Drop-in replacement | PromQL, Prometheus remote write, Jaeger, and OpenTelemetry native. Use as your single backend for all three signals, or migrate one at a time.| | 50x lower cost | Object storage (S3, GCS, Azure Blob etc.) as primary storage. Compute-storage separation scales without pain.| | SQL + PromQL | Monitor with PromQL, analyze with SQL. One database replaces Prometheus + your data warehouse.| | Sub-second at PB-EB scale | Columnar engine with fulltext, inverted, and skipping indexes. Written in Rust.|

✅ Perfect for:

• Replacing Prometheus + Loki + Elasticsearch with one database
• Scaling past Prometheus — high cardinality, long-term storage, no Thanos/Mimir overhead
• Cutting observability costs with object storage (up to 50x savings on traces, 30% on logs)
• AI/LLM observability — store and analyze high-volume conversation data, agent traces, and token metrics via OpenTelemetry GenAI conventions
• Edge-to-cloud observability with unified APIs on resource-constrained devices

Why Observability 2.0? The three-pillar model (separate databases for metrics, logs, traces) creates data silos and operational complexity. GreptimeDB treats all observability data as timestamped wide events in a single columnar engine — enabling cross-signal SQL JOINs, eliminating redundant infrastructure, and naturally supporting emerging workloads like AI agent observability. Read more: Observability 2.0 and the Database for It.

Learn more in Why GreptimeDB.

How GreptimeDB Compares

| Feature | GreptimeDB | Prometheus / Thanos / Mimir | Grafana Loki | Elasticsearch | |---|---|---|---|---| | Data types | Metrics, logs, traces | Metrics only | Logs only | Logs, traces | | Query language | SQL + PromQL | PromQL | LogQL | Query DSL | | Storage | Native object storage (S3, etc.) | Local disk + object storage (Thanos/Mimir) | Object storage (chunks) | Local disk | | Scaling | Compute-storage separation, stateless nodes | Federation / Thanos / Mimir — multi-component, ops heavy | Stateless + object storage | Shard-based, ops heavy | | Cost efficiency | Up to 50x lower storage | High at scale | Moderate | High (inverted index overhead) | | OpenTelemetry | Native (metrics + logs + traces) | Partial (metrics only) | Partial (logs only) | Via instrumentation |

Benchmarks:

• GreptimeDB tops JSONBench's billion-record cold run test
• TSBS Benchmark
• More benchmark reports

Architecture

GreptimeDB can run in two modes:

• Standalone Mode - Single binary for development and small deployments
• Distributed Mode - Separate components for production scale:
  • Frontend: Query processing and protocol handling
  • Datanode: Data storage and retrieval
  • Metasrv: Metadata management and coordination

Read the architecture document. DeepWiki provides an in-depth look at GreptimeDB: <img alt="GreptimeDB System Overview" src="docs/architecture.png">

Try GreptimeDB

docker pull greptime/greptimedb

docker run -p 127.0.0.1:4000-4003:4000-4003 \
  -v "$(pwd)/greptimedb_data:/greptimedb_data" \
  --name greptime --rm \
  greptime/greptimedb:latest standalone start \
  --http-addr 0.0.0.0:4000 \
  --rpc-bind-addr 0.0.0.0:4001 \
  --mysql-addr 0.0.0.0:4002 \
  --postgres-addr 0.0.0.0:4003

Dashboard: http://localhost:4000/dashboard

Read more in the full Install Guide.

Troubleshooting:

• Cannot connect to the database? Ensure that ports 4000, 4001, 4002, and 4003 are not blocked by a firewall or used by other services.
• Failed to start? Check the container logs with docker logs greptime for further details.

Getting Started

• Quickstart
• User Guide
• Demo Scenes
• FAQ

Build From Source

Prerequisites:

• Rust toolchain (nightly)
• Protobuf compiler (>= 3.15)
• C/C++ building essentials, including gcc/g++/autoconf and glibc library (eg. libc6-dev on Ubuntu and glibc-devel on Fedora)
• Python toolchain (optional): Required only if using some test scripts.

Build and Run:

make
cargo run -- standalone start

Tools & Extensions

• Kubernetes: GreptimeDB Operator
• Helm Charts: Greptime Helm Charts
• Dashboard: Web UI
• gRPC Ingester: Go, Java, C++, Erlang, Rust, .NET
• Grafana Data Source: GreptimeDB Grafana data source plugin
• **Grafana Dashboard