Greptime

@Greptime

The open-source observability database. One columnar engine for metrics, logs & traces on object storage. SQL across signals. PromQL for metrics.

Wolfe Road Sunnyvale

greptime.com

Joined May 2022

197 Following

1,033 Followers

Replies Reposts Media

Pinned
Greptime
@Greptime
Jun 16
GreptimeDB v1.1: you no longer have to lock in a table's partition layout when you create it. Before, only tables created with PARTITION ON COLUMNS could be resharded. Now you can take an existing single-Region table and split it online: ALTER TABLE sensor_readings
2
Greptime
@Greptime
5h
GreptimeDB v1.3: native histograms are on by default. Send them over Prometheus Remote Write v2 or as cumulative OTLP exponential histograms, then query with histogram_quantile and histogram_fraction. PromQL compliance tester: 88.7% in v1.2.1, 94.8% in v1.3 (labels and values;
Greptime
@Greptime
Nov 2
October in GreptimeDB updates: v1.3 shipped, with native histograms on by default and opt-in Trace V2. On main for v1.4: - PostgreSQL COPY FROM STDIN loads CSV and InfluxDB line protocol: ~997K rows/s vs ~47K for INSERT in the PR's benchmark - JSON2 paths can declare inverted
v1.3 GA: Native Histograms & Trace V2 | Greptime Monthly Report - No. 89
From greptime.com
1
Greptime
@Greptime
Oct 30
Your logs keep growing. Query traffic comes in peaks. Why scale storage and compute together? In 3 minutes: how GreptimeDB separates them with shared object storage in distributed deployments, and reuses data files during repartitioning.
Greptime
@Greptime
Oct 29
Observability has spent years borrowing databases built for something else. It deserves one built for it, and only for it. Greptime co-founder @killme20082 on what that commits us to. The replies show what it changes inside the engine.
Dennis Zhuang
@killme20082
Oct 29
What is an observability database? My definition: a database with unified storage and querying for metrics, logs, traces and wide events, that understands the semantics in the data and uses them to optimize storage, query execution and scaling. How it differs from what's around