Observability DB for metrics, logs, and traces

Contribute to flaneur2020/rimio development by creating an account on GitHub.

Overview

Greptime is an open-source observability database that combines metrics, logs, and traces, enabling SQL and Prom QL queries for effective data analysis.

When optimizing the write performance of GreptimeDB v0.7, we found that the time spent on parsing Protobuf data with the Prometheus protocol was nearly five times longer than that of similar products ...

One engine for metrics, logs, and traces on object storage. GreptimeDB, in Rust, aims to retire your Prometheus + Loki + Elasticsearch stack.

A step by step overview of setting coroot and greptimedb for monitoring and observability with any application. - Rituraj-Debnath/Coroot-greptimedb-setup-for-monitoring-and-observability

YouTube video by CMU Database Group

Episode · Café Debug seu podcast de tecnologia · We had a conversation with Ning Sun, Co-founder of Greptime and Observability / Time-Series Database for Scalability and we talked about Time-Series in...

Member post originally published on the Greptime blog by Lei When optimizing the write performance of GreptimeDB v0.7, we found that the time spent on parsing Protobuf data with the Prometheus protocol was nearly five times longer than...

When optimizing the write performance of GreptimeDB v0.7, we found that the time spent on parsing Protobuf data with the Prometheus protocol was nearly five times longer than that of similar products implemented in Go. This led us to consider optimizing the overhead of the protocol layer. This article introduces several methods that the GreptimeDB team tried to optimize the overhead of Protobuf deserialization.

Hi community! We have a good first issue for Rust starters to contribute at Greptime: * Merge small IO to optimize for cloud storage Thank you!

You might want to check out this blog post Diagnosing Memory Leaks with Flame Graphs and Jemalloc | Greptime which does not require tokio-console to do the profiling. I believe it works for most Rust applications. Feel free to ask if you have any question.

I have a slow memory leak, which in about 20 hours fills memory. What's current good practice on tools for finding that sort of thing? Jemalloc plus some flame graph generator is suggested in some old messages. That would be fine, but the how-to articles I've found are either old and reference nearly decade old documents. The Greptime people do this, but they're using Tokio, which I am not. Also, I need something that doesn't slow down the program much. I'm going to have to run it for hours, then stop it and check what's allocated.

This article provides a hands-on guide to integrating Rust and Java through the Java Native Interface (JNI).