🎉 after lots of work and iterations, its finally time to say goodbye to #qryn 👋 and say hello its next-gen #Gigapipe the ultimate headless polyglot stack for all of your observability needs! Easy to upgrade/migrate! 100% Open Source and faster than ever! Follow us at @gigapipe.bsky.social
It's a bit of both. This is a brand new #qryn version rewritten in golang from the ground up for the gigapipe.com service and we decided to unify the brand since qryn was really hard to google - all 100% open source as always!
The next #qryn #gigapipe release is around the corner and with it we're taking back our pioneers badge in #opensource polyglot #observability by multiplying features, boosting performance while decimating the operational costs for all of your Logs, Metrics, Traces and Profiling 👁️🗨️
gigapipe.com
about scale - qryn is particularly great at tiny setups (runs fine on RPi4, too!) and should get you the most compact setup ever (logs, metrics, traces all at once) in a single app on top of your own DB where and you own all the data in a format you can query from the side freely ;) #qryn #gigapipe
That's what we do with #qryn 👋 plus so much more
For those interested, we've been building and documenting usage of InfluxDB3 "IOx" for Metrics, Logs and Traces since 2023 here: github.com/metrico/infl...
Sadly lots of the original features are lost to commercial clouds but we have unofficial support in our polyglot observability stack #qryn
The feeling is right! We use DuckDB as #o11y storage in our #qryn polyglot observability stack already for reading data and our next-gen will offer a full in/out duckdb-parquet mode
Glad to see #qryn the original polyglot #observability stack for Clickhouse mentioned by our friends at @altinity.bsky.social
Video Link: youtu.be/lCB-3P2O8I8?...
#qryn supports HEC ingestion (through OTEL) and offers LogQL over it at this time- SPL remained a prototype plugin we never completed or released as there was little interest.
That's part of why in #qryn everything is just data stored in an OLAP database without forma lockins. The beauty of the design is our query languages are just part of the transpiler component and we can have multiple qlanguages over the same data and even across different observability types
Here's how our light polyglot #observability stack qryn compares to Grafana LGTM. #qryn transpiles Loki, Prometheus, Tempo and Pyroscope APIs, Query Languages and Protocols to/from #SQL. Use any agent you trust and own all the data stored in your OLAP database. 100% OTEL compatible. Link: qryn.dev
🚀 The #Pyroscope Extension for #DuckDB is now available on the Community Extensions repository for x86+arm64 Linux and OSX! Try it out using a free #Grafana Labs Cloud account w/ profiling token or with a local #qryn instance 🎉 @duckdb.org
#DuckDB #Telemetry #Observability #profiling #pprof
Dive deep into @duckdb.org query performance in real-time using continous profiling with the pyroscope community extension! Compatible with #qryn and Grafana Pyroscope
+1 for Rust extensions despite lacking a few features!
github.com/quackscience...
#quackscience #duckdb #pprof #grafana #pyroscope
The design of qryn is stateless so you can have as many instances as you want for reading/writing on top of the same cluster to match your needs. Writing through otel-collector is also supported for high-pressure inserts. If you need any assistance, just let us know!
#qryn
The next generation of our opensource polyglot observability stack #qryn will be (unsurprisingly) powered by #DuckDB and our quackscience extensions to provide our flagship drop-in compatibility with #Loki, #Prometheus, #Tempo, #Pyroscope APIs (in/out) on top of your data, your storage, your way 🔥
Hell Yeah! that's exactly what we're doing in our lightweight #qryn polyglot stack and its cloud twin gigapipe.com and its DuckDB super-powered next-gen version which is powered by a smart flock of parquet writers, compactors/aggregators and readers
