pretty nice extension for pi agent that has some really good prompts, tools and model routing capabilities

We created a fun little tool that lets people explore the Otel data (Traces, Logs, Metrics) they send to axiom via the console in a vi-control inspired terminal ui. As a bonus we bumped the free plan to 3 datasets so everyone can take full advantage of the ax :D

It also serves as a nice showcase what kind of tools can be built with using nothing but the public APIs

Hello friend,

I'm one of the maintainers of tremor, happy to get together and talk about rust event processing if you ever want to :)

Yeah, I'm looking forward to having further conversations once I get to know tremor.

Anyone want to learn more, come by the CNCF slack, we're in the #tremor channel :)

I'm happy to answer questions to our design.

If there are any unclear parts, I'm happy to help out.

I'm happy to answer questions to FiFo.cloud if anyone is curious :)

The post says to hurry and sign up, yet I'm not sure where I'm to be signing up for access at.

Just looking to be put on the list so I can try it out once it's released to a larger audience.

Hi sorry if the post didn't made that clean. You can sign up here: https://try.fifo.cloud/

Or feel free to shoot dm on twitter (@project_fifo) w/ your e-mail and I will make sure you get an invite :)

28 billion data points in 50 gigabytes are not impressive for time series use. That's nearly 2 bytes per data point, many time series databases achieve 1 or less byte per data point.

It's not a point, it's an entire row of data with dozens of columns and JSON.

Even if the data took twice as much space, it's still worth it to have everything in a single data warehouse with easy joins and the full expressiveness of SQL.

Outlyr has not build DalmatinerDB they've used it and contributed a bit to it.

Because labels or dimensions are not stored in as a value but as a row identifier in most implementations. That results in having to scan the entire row space and look at every row name and see if it matches the lookup.

Storing labels in a row based system (like SQL) allows querying by value, not column name which takes advantage of all optimizations and indexes making it a lot faster.

That said there is nothing forbidding someone to do both, DalmatinerDB, for example, uses a column-based format for metric values but a row-based format (PostgreSQL) for dimensions.