Elegant Observability

The standard approach to observability answers the question "what was executed." Traces show spans that describe function calls. If something isn't visible, log harvesting helps you figure it out — or it doesn't, but that’s another story.

The most troublesome errors aren't crashes, but "silent" data inaccuracies: a value is calculated, nothing crashes, yet the result is wrong — like `'1' + 1`. No one can say exactly at which step things went off the rails. And then there’s the issue of asynchrony, where a context that outlives its initial call loses its connection to the calculation result it was created for in the first place.

But observability can be improved — "supercharged" — by linking it to data and revealing exactly "what was going on." When used skillfully, the prototype chain allows you not only to store data history but also to link it to the execution flow, turning Jaeger into a reliable ally.

And yes, TypeScript helps verify all of this before runtime. All that’s left is to make it visually clear — and we’ll show you how to do that, too.

It all runs within the standard runtime — no V8 patches or other "street magic" required. Using real-world examples, we’ll explore how it works, why it’s useful, and why we simply hadn't thought of this approach before.