Self-hosted observability backend that accepts logs, metrics, traces and profiles and serves them through Loki, Prometheus, Tempo and Pyroscope compatible APIs.
GreptimeTeam/greptimedb
An open-source observability database that stores metrics, logs, and traces in one columnar engine on object storage, queryable with SQL and PromQL.
Open-source alternative to:Datadog
Grafana Cloud
- Stars
- 6,751
- Forks
- 570
- Open issues
- 326
- Last commit
- 7 hours ago
What is it?
GreptimeDB is an observability database that keeps metrics, logs, and traces in one columnar engine over object storage. All three signals share one table model made of tags, a timestamp, and fields, so when they carry common identifiers such as service, host, or trace ID, they can be correlated in SQL without moving data between systems.
It accepts data through OpenTelemetry (OTLP), Prometheus Remote Write, Loki Push, Elasticsearch Bulk, InfluxDB line protocol, and gRPC. Queries can be written in SQL or PromQL, and Jaeger-compatible trace queries and MySQL and PostgreSQL wire protocols are also supported. Storage targets S3, GCS, Azure Blob, and S3-compatible endpoints, with memory and local-disk caches in front.
The project runs in standalone mode as a single binary or in distributed mode with separate frontend, datanode, metasrv, and optional flownode components. Retention policies, downsampling, continuous aggregation, and several index types are included in the Apache-2.0 build, while read replicas and workload isolation belong to the Enterprise edition.
Key features
- 01Stores metrics, logs, and traces in one columnar engine on S3, GCS, Azure Blob, or S3-compatible storage.
- 02Ingests data via OpenTelemetry, Prometheus Remote Write, Loki Push, Elasticsearch Bulk, and InfluxDB line protocol.
- 03Supports SQL for all signals and PromQL for metrics.
- 04Correlates signals with joins on shared tags such as trace_id or service.
- 05Includes retention policies, downsampling, and continuous aggregation.
- 06Offers standalone and distributed deployment modes.
Use cases
- Replacing a Prometheus, Loki, and Tempo stack with one backend.
- Keeping long-term telemetry on object storage without a separate analytics system.
- Investigating incidents by joining error traces with the logs emitted inside them.
- Storing OpenTelemetry GenAI or agent telemetry alongside infrastructure metrics.
Quick start
- 1
Run the standalone server 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 - 2
Open the dashboard at http://localhost:4000/dashboard
Things to know
- Cluster deployment and the Flow engine are in the Apache-2.0 build, but read replicas, workload isolation and automated repartitioning are Enterprise-only.
- Some Elasticsearch and Loki query APIs are not compatible; LogQL is not supported.
- Building from source requires a Rust toolchain, a Protobuf compiler and C/C++ build tools.
Topics
FAQ
- What is greptimedb?
- An open-source observability database that stores metrics, logs, and traces in one columnar engine on object storage, queryable with SQL and PromQL. GreptimeDB is an observability database that keeps metrics, logs, and traces in one columnar engine over object storage. All three signals share one table model made of tags, a timestamp, and fields, so when they carry common identifiers such as service, host, or trace ID, they can be correlated in SQL without moving data between systems.
- Is greptimedb free to use? What license does it have?
- greptimedb is open source under the Apache-2.0 license. Check the license terms before using it in commercial products.
- Is greptimedb still maintained?
- Actively maintained. The last commit to greptimedb was on Oct 21, 2026.
- What can I use greptimedb for?
- Replacing a Prometheus, Loki, and Tempo stack with one backend. Keeping long-term telemetry on object storage without a separate analytics system. Investigating incidents by joining error traces with the logs emitted inside them. Storing OpenTelemetry GenAI or agent telemetry alongside infrastructure metrics.
- How do I install greptimedb?
- Run the standalone server 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 Open the dashboard at http://localhost:4000/dashboard
- Where can I get greptimedb?
- The source code and installation instructions are on GitHub: https://github.com/GreptimeTeam/greptimedb
Summary generated by AI from the project's README. GitHub stats refresh daily.
Related projects
Prometheus is an open-source systems and service monitoring system that collects metrics, evaluates rules, and triggers alerts.
Open-source platform to query, visualize, alert on and explore metrics, logs and traces from many data sources.
A vendor-agnostic service that receives, processes and exports traces, metrics and logs to multiple observability backends.
Datadog's open-source agent that collects metrics, logs, traces and profiles from hosts and sends them to the Datadog platform.
Open-source real-time infrastructure monitoring agent with per-second metrics, auto-discovery, built-in ML anomaly detection and alerting.