discord9 32777e458f chore(merge): merge main into narthex (#10464)
I hereby agree to the terms of the [GreptimeDB
CLA](https://github.com/GreptimeTeam/.github/blob/main/CLA.md).

## Refer to a related PR or issue link (optional)

Same shape as #10362: merge `main` into `narthex` on a branch, so the
next `narthex` → `main` PR is a mechanical replay instead of a
conflict-resolution session.

## What's changed and what's your intention?

Merges `main` (`dd941a8e334`) into `narthex` (`996b7e9e8d0`).

Since #10362, `main` moved 42 commits and `narthex` moved ahead
independently. This brings the branch back up to date so the eventual
merge back carries only narthex's own work.

### Conflicts

**Four files.**

`src/common/query/Cargo.toml` (two hunks):

- `[dependencies] futures-util`: main made it `optional = true` (only
`testing` needs it, for the hash-join fixtures); narthex declares it as
a regular dependency.
- `[dev-dependencies]`: main added `datafusion-datasource` and
`futures-util`.

Resolution: `futures-util` **stays non-optional**, because narthex's
`series_frame` API exposes `futures_util::Stream` in its public
signatures (`src/common/query/src/series_frame.rs:55`), so making it
optional would gate a production API behind the `testing` feature.
`datafusion-datasource` stays optional in `[dependencies]` and
non-optional in `[dev-dependencies]`, as main has it. The `testing`
feature becomes `["dep:datafusion-datasource"]` — the `dep:futures-util`
arm cannot stay, since Cargo rejects `dep:` on a non-optional
dependency.

`src/frontend/src/instance.rs`: import union — main added
`ServerMemoryLimiter`, narthex has `MetricDiscoveryScope`. Both kept.

`Cargo.toml` + `Cargo.lock`: follow main's newer `greptime-proto` rev
(`c46f7ee9c`, which already contains the `RawSeriesSource` that #355 put
on `main`), instead of the rev this branch merged a week ago.

`tests-integration/src/standalone.rs`: field union — `query_options`
(narthex) and `auto_create_physical_table_timestamp_unit` (main).

### What else comes along

- **DataFusion fork bump** `70f84c5b` → `638a77fb` (main moved to a
newer fork rev); the branch is rebuilt against it here rather than at
merge-back time.
- `feat: persist bounded WAL releases on region close (#10329)`,
`feat(mito2): replay pending WAL tails in the background (#10342)`,
`feat: coordinate region edits with repartition lifecycle requests
(#10354)`, `feat(query): serialize remote dynamic membership (#10341)`,
`feat(postgres): Prometheus Remote Write protobuf ingest via COPY FROM
STDIN (#10092)`, plus the auth/security fixes (`#10374`, `#10378`,
`#10382`, `#10381`) and the mito2 SST metadata work.

### Verification

- `cargo check -p common-query --all-targets --features testing` passes
(the crate one conflict was in).
- `cargo check --workspace --all-targets` passes.
- `cargo nextest run -p tests-integration -E 'test(native_aggregate)'` →
6/6 passed.

The first push of this branch had a genuine red:
`native_aggregate_complete_over_four_nonempty_mito_partitions` failed
because four tests still asserted the pre-#10418 topology. That is fixed
by #10466 (merged into `narthex`); this branch is rebased onto it, and
the same local run is green.
- `Cargo.lock` regenerated with `cargo metadata`; no manual edits.

## PR Checklist
Please convert it to a draft if some of the following conditions are not
met.

- [ ] I have written the necessary rustdoc comments.
- [ ] I have added the necessary unit tests and integration tests.
- [ ] This PR requires documentation updates.
- [x] API changes are backward compatible.
- [x] Schema or data changes are backward compatible.
- [ ] This PR needs to be backported to release branches, and I have
added the `backport-<target>` labels (e.g. `backport-v1.3` targets
`release/v1.3`).

## Merge timing

- [ ] Merge during the nightly window <!-- nightly-merge -->
2026-11-17 10:16:40 +08:00
2023-08-10 08:08:37 +00:00
2026-11-17 10:13:41 +08:00
2026-11-17 10:13:41 +08:00
2026-11-17 10:13:41 +08:00
2026-11-17 10:13:41 +08:00
2026-11-17 10:13:41 +08:00
2026-11-17 10:13:41 +08:00
2023-06-25 11:05:46 +08:00
2026-11-17 10:13:41 +08:00
2026-11-17 10:13:41 +08:00
2023-11-09 10:38:12 +00:00

GreptimeDB Logo

Metrics, logs, and traces.
One engine, on your infrastructure.

User Guide  ·  API Docs  ·  Live Demo  ·  Roadmap 2026  ·  Slack

Stable Canary Nightly Docker Pulls License

stable for production  ·  canary includes pre-releases  ·  nightly is a weekly snapshot of main

Introduction

GreptimeDB is an open-source observability database. Metrics, logs, and traces run on one columnar engine over object storage and share one table model: tags, timestamp, and fields. When signals carry common identifiers such as service, host, or trace ID, you can correlate them in SQL without moving data between databases.

Ingest through OpenTelemetry, Prometheus Remote Write, Loki Push, or Elasticsearch Bulk. Use SQL across observability data and PromQL for metrics. Migrate ingestion one signal at a time without rebuilding your collectors.

One Query Across Signals

OpenTelemetry ingestion writes spans to opentelemetry_traces and log records to opentelemetry_logs. Both tables carry trace_id, so correlating them is a join:

-- The slowest failed spans in the last hour,
-- with the log lines emitted inside those same traces.
SELECT
    t.service_name,
    t.span_name,
    t.duration_nano / 1000000 AS duration_ms,
    l.timestamp AS log_time,
    l.severity_text,
    l.body
FROM opentelemetry_traces t
JOIN opentelemetry_logs l ON l.trace_id = t.trace_id
WHERE t.timestamp > now() - INTERVAL '1' HOUR
  AND t.span_status_code = 'STATUS_CODE_ERROR'
ORDER BY t.duration_nano DESC
LIMIT 20;

Metrics join the same way, on any tag the tables share, such as service, host, or pod.

Try GreptimeDB

For AI agents — paste this prompt into your agent:

Read https://docs.greptime.com/SKILL.md and follow the instructions
to deploy, configure, ingest, and query 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 \
  --grpc-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
Or skip the install and try the Live Demo.

Next: Quickstart, the full Install Guide, Demo Scenes, and the FAQ.

Why You Might Use It

  • You run Prometheus plus Loki or Elasticsearch and want one backend instead of three
  • You have outgrown Prometheus on cardinality or retention and don't want the Thanos/Mimir operational surface
  • You are hitting Loki's query performance limits as log volume grows
  • You need long retention on object storage without a separate analytics stack
  • You want to query telemetry with SQL, not only a domain query language
  • You are storing GenAI or agent telemetry (OTel GenAI conventions) alongside infrastructure signals

Learn more in Why GreptimeDB.

What's Supported

Ingest OpenTelemetry (OTLP), Prometheus Remote Write (with native histograms over Remote Write 2.0), Loki Push, Elasticsearch Bulk, InfluxDB line protocol, gRPC
Query SQL, PromQL, Jaeger-compatible trace queries, MySQL and PostgreSQL wire protocols
Storage S3, GCS, Azure Blob and S3-compatible endpoints as primary storage, with memory and local-disk caches
Built in Pipelines that parse and transform logs at ingestion, retention policies, downsampling, continuous aggregation, explicit table partitioning, and inverted / skipping / fulltext indexes

Compute and storage are disaggregated: object storage holds the data, while memory and local-disk caches keep recent and frequently queried data close to compute.

GreptimeDB Overview

Benchmarks

Compatibility and Migration

Compatibility is per protocol, and query-side coverage is narrower than ingestion.

Compatible Not compatible
Prometheus Remote Write ingestion; PromQL queries Gaps are listed in PromQL compatibility
Loki Push ingestion; dual-write through Grafana Alloy makes the cutover gradual LogQL and the rest of the Loki query API
Elasticsearch _bulk ingestion in the open-source core; QueryDSL partially, in Enterprise Most other Elasticsearch APIs

Limitations and Edition Boundary

Cluster deployment, object storage, the Flow engine, and every ingestion protocol listed above are in the Apache-2.0 build. Repartitioning and region migration are manual operations there.

Read replicas, workload isolation, and automated repartitioning are GreptimeDB Enterprise features, along with enterprise security and governance. The Enterprise overview has the current list, and pricing has the edition comparison. For GreptimeDB Enterprise inquiries, contact us.

Architecture

GreptimeDB can run in two modes:

  • Standalone — single binary for development and small deployments.
  • Distributed — four components, each independently scalable:
    • Frontend — protocol endpoints and the distributed query engine. Stateless, scales horizontally.
    • Datanode — region engine with WAL, memtable, SST, cache, compaction, and indexes. Persists data to object storage.
    • Metasrv — metadata, region routing, and cluster coordination (DDL procedures, failover, region migration, repartitioning). Backed by a pluggable KV layer (etcd or RDS).
    • Flownode (optional) — continuous flow computation (streaming and materialized views).

For deeper coverage, see the architecture doc or DeepWiki.

GreptimeDB System Overview

Build From Source

Prerequisites:

  • Rust toolchain — stable, pinned by rust-toolchain.toml
  • Protobuf compiler (>= 3.15)
  • C/C++ building essentials: gcc / g++ / autoconf and the glibc dev package (libc6-dev on Ubuntu, glibc-devel on Fedora)
  • Python toolchain (optional, only for some test scripts)

Build and run:

make                          # build greptime binary
cargo run -- standalone start # start in standalone mode

Common dev commands:

make fmt            # format Rust code
make clippy         # lint (fails on warnings)
make test           # unit + integration tests (uses cargo-nextest)
make sqlness-test   # SQL regression tests

See the Contribution Guidelines for the full developer workflow.

Tools & Extensions

Project Status

GreptimeDB is generally available, with stable APIs and regular releases. It runs in production at scale — OceanBase Cloud operates 80+ GreptimeDB clusters managing 300 TB of logs, cutting log storage cost by 60%+ after migrating from Grafana Loki. See more in case studies.

Releases follow Semantic Versioning. For where the project is going, read the v1.0 highlights, the 2026 roadmap, and what we mean by an observability database.

Community

If GreptimeDB is useful to you, please star the repo.

Star History Chart Known Users

License

GreptimeDB is an open-core project. Its core is licensed under the Apache License 2.0.

A small set of peripheral, enterprise-only features are gated behind the enterprise Cargo feature (not built by default) and are governed by the separate GreptimeDB Enterprise License. Source files under that license carry an explicit Enterprise License header.

Contributing

Integration CI Codecov

Acknowledgement

Special thanks to all contributors! See AUTHOR.md.


All trademarks, logos, and brand names referenced in this README and in the Overview diagram are the property of their respective owners. Their use is for identification purposes only and does not imply endorsement or affiliation.

S
Description
Open-source, cloud-native, unified observability database for metrics, logs and traces, supporting SQL/PromQL/Streaming.
Readme Apache-2.0
2 GiB
Languages
Rust 97.4%
Python 1.8%
Shell 0.4%
JavaScript 0.2%