Launching today
SketchLog
Bounded-memory telemetry for observability
12 followers
Bounded-memory telemetry for observability
12 followers
SketchLog is an open-source observability platform for compact telemetry summaries. It uses sketch data structures to answer production questions like p95/p99 latency, unique users, top events, anomaly movement, SLO burn, and streaming SQL without storing every raw event forever. It includes a hosted playground, dashboards, PostgreSQL durability, optional OmniKV embedded storage, SDKs, WebAssembly, Docker, Helm, Kubernetes docs, and proof-first CI/release checks.
A hosted tier with a free usage cap beyond the playground would be a nice way to actually try SketchLog on real traffic before committing to self hosting. Right now jumping from the demo straight to Kubernetes feels like a big leap.
@oktay371908 I agree. The hosted playground is useful for understanding the workflows, but a small hosted tier with a free usage cap would make it much easier to test SketchLog on real traffic.
Right now the project is focused on open-source/self-hosted proof paths, but a hosted evaluation tier is definitely one of the most important next steps.
Loaded up the playground and ran a streaming SQL query against some sample telemetry, the response time felt surprisingly snappy for sketch-based storage. Curious how it holds up once I point our own SDKs at it on a real workload.
@pekxyi5 Thank you for trying it. That is exactly the direction I want SketchLog to go: fast operational questions over compact telemetry summaries.
The next thing I want to prove more deeply is behavior under real SDK-driven workloads, including sustained ingestion, query latency, storage backend differences, and memory usage over time.
One thing I'd love to see is a built-in cost estimator that shows how much storage and compute each sketch configuration would consume before you deploy it, especially since the whole pitch is about not storing every raw event.
@ceylinegil91932 Thanks, this is a very good point. A built-in cost estimator fits SketchLog really well because bounded-memory telemetry should be understandable before deployment, not only after running it.
I’m thinking of adding a calculator that estimates memory, storage, and compute based on stream count, sketch accuracy, retention windows, tenants, and backend choice. This would make the “why not store every raw event?” tradeoff much more concrete.