Today, I found a bug before I noticed it. Like, it was subtle, and so I wasn’t quite sure I saw it–maybe I hadn’t hit refresh yet? Later, I looked at the trace of my function and boom, there was a clear bug. Here’s the function with the bug. It responds to a request to …
What is happening in production? Distributed tracing can help you find out. But it’s one thing to instrument, another to use it. Here’s a short (6m) video that asks “Why is this so slow?” See three quick ways to get answers in Honeycomb. If you want to follow along and play with the same data …
Honeycomb made it suuuuuper easy to see traces of HTTP requests hitting my app. Right from my computer! We installed one gem, did one rails generate from a cut-and-paste their dataset creation page gave me. Start up rails server, hit http://localhost:3000, and boom! A thing on a graph in Honeycomb! That was cool. Except, um, …
Read moreHoneycomb in Rails with separate dev and production events
Today we hooked up Honeycomb to an app for the first time! It was easy and fun! Then we configured it so that we don’t have to commit our apikey. It’s a public repo. Anyone could grab our API key and send spurious events to our Honeycomb datasets, screwing up our information and costing us …
Legacy code is software that is no longer alive in someone’s head. No person has a mental model of how it works, no one has the stories of why. This is already the common case in software systems, and it will only grow more normal. Understanding an entire piece of the system is a luxury. …