Back to browse
GitHub Repository

Free, open-source OpenTelemetry backend powered by DuckDB πŸ¦† and SQLite

19 starsClojure

OpenTelemetry x DuckDB(Ducklake) x Clojure

by mnmingΒ·May 10, 2026Β·3 pointsΒ·0 comments

AI Analysis

●●●BangerBig BrainZero to OneSolve My Problem

Replaces ClickHouse clusters with a single DuckDB container handling 140K events/sec on an M1 Max.

Strengths
  • β€’Automatic schema evolution turns new telemetry fields into queryable columns without migration.
  • β€’Wide events pattern support stores rich context in single records instead of scattered logs.
  • β€’Native agent interface with OAuth PKCE lets LLMs query telemetry and manage alerts directly.
Weaknesses
  • β€’Single-process architecture may hit ceiling for enterprise-scale multi-node requirements.
  • β€’DuckLake storage backend is relatively new compared to battle-tested Parquet ecosystems.
Target Audience

DevOps engineers and homelab enthusiasts tired of complex observability stacks

Similar To

Honeycomb Β· Grafana Tempo Β· ClickHouse

Post Description

O11yLite is a free, open-source OpenTelemetry backend built on DuckDB/Ducklake, SQLite, Clojure.

I started this as a project to build an observability stack for my homelab. After years of using the established OSS tools, they felt fragmented, had a steep learning curve, and often inflexible. I wanted to build a Honeycomb-like experience that unifies logs, metrics, and traces in a single tool that can be as easy to deploy as possible and free.

Specifically, I wanted it to - work well with the wide events pattern. - have sufficiently high throughput on a single host. - treat both human and agent interfaces as first-class citizens.

I initially planned to build on ClickHouse, but switched to DuckDB to keep distribution dead simple. I was also inspired by Motherduck's [Perf is not enough](https://motherduck.com/blog/perf-is-not-enough/) post. When DuckLake came out around the same time last year, it felt like the right foundation had just arrived. How good would it be if your OpenTelemetry backend just operate on a directory of Parquet files? So here it is: a small, open-source tool in an era where LLMs dominate the headlines. Hope some people find it useful.

Similar Projects