ex. we just hardcoded the UI to use the duration column, but it accepts anything really: github.com/hyperdxio/hy...
we'll just need to wire another input component - it sounds like it might be pretty useful so maybe we'll squeeze it in before the next beta version cut!
Ah I just clarified that in another thread. In ClickHouse it's straightforward as nothing is special about the duration column, we simply didn't implement the UI for the first iteration of this release (the current iteration is ~a day of work we squeezed pre-launch, the "backend" is already generic)
👀 our selection isn't arbitrary! though we do the property selection post-sampling and refine ordering based on value deltas, in Honeycomb's case it sounds like those decisions are made pre-sampling?
I assume in most cases it'd resolve in pretty similar experiences, but I'd love to learn more
Not a DB limitation, our query generation is generic for heatmaps but wanted to keep the feature scoped to the most common use case of duration. This is our first cut of the v2 beta, lots more to come!
It's always validating to hear that people want more 😃 would love to learn more of your thoughts