Nicheloom

Market intelligence for builders — see what's gaining traction before it's crowded.

Oodle

Unified Debugging with OpenSearch and Grafana

Details

External ID
45812312
Source
HN
Company
—
Product
Oodle
Website domain
oodle.ai
Launched
Nov. 4, 2025
Cohort
—
Upvotes
11
Upvotes percentile
0.5447598253275109
Tags
—
Fetched at
Sept. 7, 2026, 9:25 p.m.
Updated at
Sept. 7, 2026, 9:25 p.m.

Description

Hey HN -Kiran and Vijay here.We built Oodle after seeing teams forced to choose between low cost, great experience, zero ops, and no lock-in. Even with premium tools, debugging still meant switching between Grafana for metrics, OpenSearch for logs, and Jaeger or Tempo for traces - copying timestamps, losing context, and burning time during incidents.So we decided to rethink observability from first principles - in both architecture and experience.Architecturally, we borrowed ideas from Snowflake: separated storage and compute so each can scale independently. All telemetry - metrics, logs, and traces - is stored on S3 in a custom columnar format, while serverless compute scales on demand. The result is 3–5× lower cost, massive scale, and zero operational overhead, with full compatibility for Grafana dashboards, PromQL, and OpenSearch queries.On the experience side, Oodle unifies everything you already use. It works with your existing Grafana and OpenSearch setup, but when an alert fires, Oodle automatically correlates metrics, logs, and traces in one view - showing the latency spike, the related logs, and the exact service that caused it.It’s already in production across SaaS, fintech, and healthcare companies processing 10 TB+ logs/day and 50 M+ time-series/day.We’ve both spent years building large-scale data systems. Vijay worked on Rubrik’s petabyte-scale file system on object storage, and I helped build AWS S3 and DynamoDB before leading Rubrik’s cloud platform. Oodle applies the same design principles to observability.You can try a live OpenTelemetry demo in < 5 minutes (no signup needed): https://play.oodle.ai/settings?isUnifiedExperienceTourModalO...or watch a short product walkthrough here: https://www.youtube.com/watch?v=wdYWDG3dRkUWould love feedback - what’s your biggest observability pain today: cost, debuggability, or lock-in?

Enrichment

Theme
lightweight and on-device AI runtimes
Vertical
Horizontal
Function
Observability & eval
Audience
Developer
AI stance
Not AI
Project type
Commercial product
Normalized one-liner
unified debugging tool with opensearch and grafana
Manually corrected
False

Could you build this?

Partial While an interface querying Grafana, OpenSearch, and Jaeger APIs can be vibe-coded, maintaining production-grade cross-telemetry correlation and real-time observability ingest pipelines requires substantial distributed systems work.

What it would actually take: A production implementation requires an OpenTelemetry-compliant ingest pipeline (Kafka/ClickHouse/OpenSearch) alongside an orchestration layer to join traces, logs, and metrics across disparate storage backends. The difficult engineering lies in scalable distributed log indexing, low-latency cross-correlation across high-cardinality telemetry datasets, and reliable multi-tenant infrastructure.

Discussion

3 comments analyzed.

Competitors mentioned: disk-based data stores, serverless functions/lambdas for querying

Concerns raised: handling ephemeral labels causing cardinality spikes, scaling with high-cardinality metrics, in-memory index size management

Feature requests: store high-cardinality metrics on disk without in-memory index

Competitors

Other products that read as similar to this one — 65 launches clear the similarity bar, closest 8 shown.

Attention rank: #44 of 66 (itself plus its competitors, highest first — normalized so YC and Product Hunt are compared fairly).

Launched 3 days after the earliest competitor.

Other launches for this product

Same idea, different domain

Nobody's really built a observability & eval tool for Media & entertainment yet.