Dennis Zhuang
@killme2008.bsky.social
CEO & Founder @ Greptime. Engineer, petrohead and tifosi.
github.com/killme2008
greptime.com
github.com/killme2008
greptime.com
The OpenTelemetry demo ships with three storage backends: Jaeger for traces, OpenSearch for logs, Prometheus for metrics.
I swapped all three for one GreptimeDB standalone. The collectors didn't change , only the write address moves.
greptime.com/blogs/2026-0...
#OpenTelemetry
I swapped all three for one GreptimeDB standalone. The collectors didn't change , only the write address moves.
greptime.com/blogs/2026-0...
#OpenTelemetry
September 16, 2026 at 8:39 AM
The OpenTelemetry demo ships with three storage backends: Jaeger for traces, OpenSearch for logs, Prometheus for metrics.
I swapped all three for one GreptimeDB standalone. The collectors didn't change , only the write address moves.
greptime.com/blogs/2026-0...
#OpenTelemetry
I swapped all three for one GreptimeDB standalone. The collectors didn't change , only the write address moves.
greptime.com/blogs/2026-0...
#OpenTelemetry
Reposted by Dennis Zhuang
GreptimeTeam / greptimedb: The open-source observability database. One columnar engine for metrics, logs, and traces, on object storage. ★6605 https://github.com/GreptimeTeam/greptimedb
GreptimeTeam / greptimedb
The open-source observability database. One columnar engine for metrics, logs, and traces, on object storage.
github.com
September 4, 2026 at 11:36 AM
GreptimeTeam / greptimedb: The open-source observability database. One columnar engine for metrics, logs, and traces, on object storage. ★6605 https://github.com/GreptimeTeam/greptimedb
Last post in my observability unification series.
The uncomfortable question: LLMs already know OTel semantic conventions, Prometheus metric types, how traces fit together. So what's actually left for the database to do?
My answer is deliberately small. Two things.
blog.fnil.net/what-is-left...
The uncomfortable question: LLMs already know OTel semantic conventions, Prometheus metric types, how traces fit together. So what's actually left for the database to do?
My answer is deliberately small. Two things.
blog.fnil.net/what-is-left...
LLMs Already Understand Observability. What Is Left for the Database?
The last post in this series. The time for unified observability has come, so what should a database actually do about it? My answer is probably smaller than you expect, and "doing less" is what I arr...
blog.fnil.net
September 2, 2026 at 8:51 AM
Last post in my observability unification series.
The uncomfortable question: LLMs already know OTel semantic conventions, Prometheus metric types, how traces fit together. So what's actually left for the database to do?
My answer is deliberately small. Two things.
blog.fnil.net/what-is-left...
The uncomfortable question: LLMs already know OTel semantic conventions, Prometheus metric types, how traces fit together. So what's actually left for the database to do?
My answer is deliberately small. Two things.
blog.fnil.net/what-is-left...
I used to think wide events would absorb metrics, logs and traces. After this year, I don't.
They're their own signal with their own shape — clearest in what AI agents emit. Complement, not replace.
We've argued the stronger version on our own blog. This is me updating.
They're their own signal with their own shape — clearest in what AI agents emit. Complement, not replace.
We've argued the stronger version on our own blog. This is me updating.
September 2, 2026 at 2:19 AM
I used to think wide events would absorb metrics, logs and traces. After this year, I don't.
They're their own signal with their own shape — clearest in what AI agents emit. Complement, not replace.
We've argued the stronger version on our own blog. This is me updating.
They're their own signal with their own shape — clearest in what AI agents emit. Complement, not replace.
We've argued the stronger version on our own blog. This is me updating.