Thread by @mipsytipsy

HEY: did you read my post on the power of rich, wide events, then close the tab sighing "yeah, I get it, but we are just never gonna re-instrument that code"?

Then you need to see this detailed demo from @cribl_io, as they literally do it for you. blog.cribl.io/2019/03/04/con…

There are a lot of you out there in this situation. And I get it. We have greased the path to rich instrumentation about as much as humanly possible with beelines -- it's dead fucking simple, install a library -- but sometimes even that is too much friction.

I get it, I do.

The @cribl_io folks are coming at the same problem from another angle. They'll take whatever garbage you are emitting, using best practices of a decade or two past -- and swiftly reassemble it into the rich, wide events you need for modern observability.

The demo shows taking old log output, transforming with @cribl_io, and streaming it into @honeycombio just as though you had painstakingly instrumented the code.

Look how powerful that limp old spew becomes with a bit o'structure and modern tooling. ✨🤗 zero code changes! 🤗✨

What I love about these kids is that they are ex-splunk. This enterprise/logs shit is in their DNA, they already have the right scars.

They are way better equipped to be a bridge from that world to @honeycombio and the future than we are, so let's each do what we do best.

If you want @cribl_io's help moving your mountains of enterprise logs over to honeycomb, hit them up.

(Or if you're tired of paying so much in ransom. This way is not only easier and better, it is 💰💰cheaper💰💰. Get a quote.)