GreptimeTeam

greptimedb: Store and Query Metrics, Logs, and Traces

GreptimeDB is a Rust observability database that stores metrics, logs, and traces on object storage. It suits teams seeking a shared backend for telemetry, with SQL and PromQL queries and support for common ingestion protocols.

View on GitHub Compare
Stars
6.7k
Forks
556
Stars, last 30 days
+72

Our take

Health score

80/100

How it is scored
Activity
86
Community
93
Issues
78
Pull requests
64

+72 stars in the last 30 days

  • Merges more pull requests than 93% of the projects we track
  • Releases more often than 89% of the projects we track
  • More contributors than 78% of the projects we track

Project history

Daily GitHub snapshots since Oct 7, 2026. History covers stars and forks; health signals are not tracked historically.

Selected snapshot

Stars

6,813

Forks

584

Change since Nov 15, 2026: +1 stars·+1 forks

Overview

GreptimeDB is a columnar database for observability data. It brings metrics, logs, and traces into one engine and table model, so teams can query and correlate signals without maintaining separate backends for each type.

It is designed for deployments that need long-term storage on object storage, high-cardinality telemetry, or SQL access alongside PromQL. It can run as a standalone binary or as a distributed cluster.

Key Features

  • Ingest telemetry through OpenTelemetry, Prometheus Remote Write, Loki Push, Elasticsearch Bulk, and InfluxDB line protocol.
  • Query data with SQL and PromQL, with MySQL and PostgreSQL wire protocols available.
  • Join logs and traces, or other telemetry tables, using shared identifiers such as trace IDs and service names.
  • Store data on S3, GCS, Azure Blob, or compatible object storage, with memory and local-disk caches.
  • Use retention policies, downsampling, continuous aggregation, partitioning, and data indexes.
  • Deploy in standalone mode or scale a distributed deployment across frontend, datanode, and metadata components.

Use Cases

  • Observability teams can consolidate metrics, logs, and traces in one backend instead of operating separate databases.
  • Teams with high-cardinality metrics or retention needs can use object storage for durable telemetry storage.
  • Engineers investigating incidents can query and correlate trace and log records with SQL.
  • Organizations adopting OpenTelemetry can route telemetry to a shared database while using supported ingestion protocols.

Getting Started

Run a standalone instance with Docker:

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 \
  --grpc-bind-addr 0.0.0.0:4001 \
  --mysql-addr 0.0.0.0:4002 \
  --postgres-addr 0.0.0.0:4003

See the repository README and installation guide for setup and configuration details.

Alternatives

  • prometheus/prometheus: Prometheus focuses on collecting and querying metrics, while GreptimeDB also stores logs and traces and targets shared telemetry storage.
  • ClickHouse: ClickHouse is a general-purpose analytical database used for observability workloads, while GreptimeDB is purpose-built for metrics, logs, and traces.
ProjectLanguageLicenseStarsStatus
greptimedbRustApache-2.06.7kNot checked yet
prometheus/prometheusGoApache-2.066.3kActive
ClickHouseC++Apache-2.050.7kActive

Considerations

  • Query compatibility varies by protocol. For example, PromQL has documented gaps, and Loki Push ingestion does not provide LogQL or the full Loki query API.
  • The Apache-2.0 core includes cluster deployment and object storage, but read replicas, workload isolation, automated repartitioning, and some security and governance features are Enterprise features.
  • Repartitioning, region migration, and index creation are manual operations in the open-source build.
  • Building from source requires a Rust toolchain and Protobuf compiler, plus C/C++ build essentials.

Found this useful?

Share it with someone who would like greptimedb.

Comparisons