2) if it were possible, you would never pay to collect and store it all
3) even if you could pay, "logging" only solves the easy part. Now you get to solve "finding all the right bits of data, at the right time, in a timely manner". 🌷☺️
honeycomb.io/blog/lies-my-p…
Even though you could totally think of honeycomb events as structured logs, or stream your structured log into honeycomb just fine. So why not call it logging?
* unstructured strings
* spewing to local disk
* emitted willy-nilly thru the execution path, each line containing just a few nouns of detail
And honey libs emit only one event per request per service,
It's not unthinkable to call what honeycomb does "logging". But if a term contradicts all your assumptions in reality, maybe it's not the right term.
Anyway, I forget where I was going with this, so I'll just say that logs (unstructured strings, flushed to disk) ought to die in a fire with all the rest of 80s tech innovations. They are wasteful and messy,
Better mental model preserves request context (honeycomb, that @lyddonb talk I'm always citing, etc). Also having a place: counters/gauges (metrics), and a debugger to step thru execution.
This trains you to debug by intuition + by searching for a string you already know to exist.
(Microservices are often a tipping point.)
Instead of grepping for something that gets you within spitting distance of the problem, you... can't do that, because you have no idea what the problem is.
So you have to start at the top, with this rando spike, and trace it down to
* a particular user?
* coming from/going to an IP?
* a particular client, or client version?
* handled by an older app version?
* unhandled language type?
* hitting a shard where a migration hasn't run yet?
* any combination or subset ^?
In distributed systems, that's called a "Wednesday".
But it is a sequence of high cardinality queries, and your tools havent supported that. You have been
Now think how much time you could reclaim to use on better things if you used @honeycombio. ☺️ honeycomb.io/signup
"FUCK LOGS"
??!!? Or better yet..
"Fuck strings. Fuck debugging. Fuck a job. Fuck a career. Fuck an indecipherable amorphous mess of remnants of once-proud thoughts. FUCK LOGS"