Viewing profile — mvijaykarthik

We store these files on S3 and directly read them in the query path using lambda functions. Parquet would work as a storage format for logs and traces, but not for metrics. At oodl…

We price per GB of ingested trace - $0.3/GB, goes lower as you scale. Traditional APM spans are ~2KB - this would come to ~$0.6/million spans. How we arrived at $10 is that we assu…

Hi HN, Vijay here Adding support for agent traces turned out to be a great learning experience - it pushed us to rethink and replace parts of our storage engine https://blog.oodle.…

For more info and examples - https://blog.oodle.ai/high-performance-in-golang/#memory-all...

Frequent memory allocations can be costly in Go. Go's sync.Pool helps with object reuse but isn't type-safe and can introduce bugs. You need type assertions, and it's easy to accid…

1. We store high cardinality metrics in object storage and only keep most recent data in memory. We use serverless functions (lambdas) for querying these objects which helps us sca…

Thanks for your feedback, and great questions. 1. We create serverless functions to process each file and then combine the results, optimized for columnar file formats. 2. This is …

We are reasonably close to the latest version of Grafana. We periodically pull in new changes.

We are still early in our journey, and are currently working on leveraging LLMs for incidents and query / dashboard generation. We do use pre-LLM-era AI and statistical analysis to…

Oodle can be utilized solely as a datasource, but we also wanted to provide a solution for customers who don’t have a visualization platform in place. Here is the branch we use: ht…

Technically you are correct, the scraper will still exist. However, the hard part is scaling the query and storage layers which we replace.

We use a local disk to temporarily stage data before putting it on S3. We have smaller WAL (write ahead log) objects, and a periodic compaction process which creates read-optimized…

Great question! Vijay here, I'm one of the co-founders of Oodle. Compared to thanos 1. We use object store (S3) for all queries - even recent time ranges. Object store is not just …

Good question! Scraping and ingestion continues to use dedicated compute. Serverless helps with query performance. Queries can be parallelized with serverless functions, this espec…

About Oodle: Oodle is a fully managed, serverless metrics observability platform. It is a drop-in replacement for Prometheus that delivers fast performance at high scale. Oodle is …

I've added a section in the README for this. It works in conjunction with NTPD and the time provided by this library has some extra guarantees like monotonicity, immunity to large …

We recently open-sourced https://github.com/rubrikinc/kronos for the exact same problem. Coincidentally I shared that on Show HN just today: https://news.ycombinator.com/item?id=18…

Hi HN, we at Rubrik have created this library which we use with CockroachDB to avoid issues with clock skews impacting service availability. Let us know if you have any questions!