This is worth underlining for a few reasons. Tracing in a distributed system is so, so, so, SO valuable. Christ. It is the Swiss army knife of tools, and every engineer pushing code should be tracing that code erry gorram day as a habit of hygiene, like brushing your teeth.
So WHY IS IT that tracing is the least democratized tool I have ever seen?
Why is it that, instead of every engineer keeping a tracing tab open and pinned, every shop has one or two tracing priests who everyone else goes to for help tracing their shit as a last resort?
Why is it that, instead of every engineer keeping a tracing tab open and pinned, every shop has one or two tracing priests who everyone else goes to for help tracing their shit as a last resort?
I mean, I have many theories. 🙃 But more importantly, we aim to change that.
* by making it dead easy to roll out (and compatible with all the other tracing shit, in case you've already deployed that)
* by making it easy to search for traces you ~and your team~ have run before
* by making it dead easy to roll out (and compatible with all the other tracing shit, in case you've already deployed that)
* by making it easy to search for traces you ~and your team~ have run before
* by integrating traces seamlessly into other modes of debugging, so that you shift back and forth effortlessly
* by removing the friction of having to switch tools and copy paste ids by hand 🙇♀️🙇♀️🙇♀️
* by not having to maintain multiple instrumentation modalities
* by removing the friction of having to switch tools and copy paste ids by hand 🙇♀️🙇♀️🙇♀️
* by not having to maintain multiple instrumentation modalities
* by making it so you can usefully aggregate traces and search within them
* by making it friendlier and less hostile to users, less of an “elites only” tool
... and so on. Yes, you should be instrumenting tests with tracing. Yes, you should instrument your CI/CD pipeline.
* by making it friendlier and less hostile to users, less of an “elites only” tool
... and so on. Yes, you should be instrumenting tests with tracing. Yes, you should instrument your CI/CD pipeline.
And a million other things that will occur to you once the hammer is in your daily toolbox.
After all, tracing is only useful when it comes to problems that have anything to do with, um.. code execution, or not- execution? Niche stuff. 😉
After all, tracing is only useful when it comes to problems that have anything to do with, um.. code execution, or not- execution? Niche stuff. 😉
