When we released derived columns last year, we already knew they were a powerful way to manipulate and explore data in Honeycomb, but we didn’t realize just how many different ways folks could use them. We use them all the time to improve our perspective when looking at data as we use Honeycomb internally, so we decided to share. So, in this series, Honeycombers share their favorite derived column use cases and explain how to achieve them.

Our new RubyGems.org public dataset is now available — use it to analyze global download traffic of all gems hosted on RubyGems!

Honeycomb strives to be a fast, efficient tool; our storage back-end satisfies the median customer query in 250ms (and the P90 in 1.3 seconds). Still, every system has its limits, and customers with large datasets know that querying over a long time range, grouping by high-cardinality columns, building complex derived columns, and throwing a quantile or heat map into the mix can lead to some pretty slow queries. If this sounds familiar: good news!

When we release something new, whether it’s a new SDK or Beeline or a new feature in the UI, we’ll often set a Honeycomb Trigger to keep track of its use. Sometimes we don’t necessarily have a customer we know is immediately going to use the feature in question, and we’re interested in when it happens.

If you’ve been paying attention, you know that although collecting and reviewing metrics and logs is a core part of running a stable and successful service, access to raw events and the ability to search and pivot on any dimension of your production environment, no matter how high-cardinality, is what will help your team debug and troubleshoot new problems and outages more quickly.

We’ve seen folks do amazing things using our Honeycomb Beelines–getting their apps instrumented in next-to-no time, expanding their observability, growing their understanding of what is happening in their code in production. Now, prepare to do more with improved tracing support!

We recently shipped an update to navigating inside Honeycomb. Thus far, results have been positive – thank you! We wanted to give you a behind the scenes look at why and how this work came along. It’s easy to develop a certain blindness after working with your own code day-in day-out. Staring at something over a long period of time wears down the jagged edges that once used to protrude and now appear as normal.

Here at the Hive, we know that there’s nothing like getting your hands on something to see what using it to solve a problem is really like. In July, we launched the Gatekeeper tour, which walks you through the process of solving a real outage we experienced, using Honeycomb. That’s why we’re excited to launch a new place for you to play: the Tracing Tour at http://play.honeycomb.io.

Here at Honeycomb, we spend lots of time thinking about how to help our users be more awesome at unearthing insights from their data so they can solve production issues in real-time. We think a lot about how to make running a query easy, how to guide users to wield our Query Builder effectively to find the needles in the haystacks of data that they send us.

As we are fond of saying here at Honeycomb, context is king, and one of our favorite ways to share the context in our brains is with Boards. We recommend using Boards to share query structures you’ve developed for reuse, share visual graphs for ongoing review of systems, share your brain with your colleagues…and your future self.