Frozen Moment
Hit pause and the incident stops around you. The queue still backing up, the deploy still mid-roll, checkout gone quiet: all of it held exactly where it was, while you walk over and look at each one.
Start FreeThe distributed trace is the best thing the flat tools ever built, and it deserves saying plainly: a real join of every span of one request, in order, the closest anyone has come to holding a moment still. Keep using it. What it cannot give you is everything else that was happening while that request broke. A trace is one thread through the incident. The incident was a room.
- A trace gives you the thread. A frozen moment gives you the room. Stand at the failing service, hit pause, and its neighborhood is held around you: the queue backing up while the deploy rolled and checkout went quiet, each in its place. Whoever arrives brings judgment and finds the rest already gathered.
A pause is not a place
Stop a feed and you are outside it looking at a still image; stop a world and you are standing in it
Everything stops. You do not.
This is the part that is hard to picture until you have done it.
- The whole scene holds: hit pause and every animation stops. Nothing new arrives. Nothing already there fades, decays, or gets pruned away while you are looking at it.
- And you can still move: it is a freeze-frame you walk around in. Go over to the queue. Look at the deploy from the other side. The moment does not run away while you cross the room.
- Every actor at once: not six panels aggregating separately while you perform the join in your head. The join already happened, and it is laid out around you.
A trace is one request's thread
What it cannot give you is the neighborhood around that thread while it broke
The handover stops being a story
You do not describe the incident. You leave it standing.
- The scene survives the explanation: the person who arrives at 3am does not need you to narrate what you saw. It is still there, held, and they can walk it themselves.
- Nothing recedes when you look away: a paused stream resumes and is gone. A held scene is a place, so what you had already ruled out is still ruled out when you come back to it.
- Your partner is in the same room: where you are standing is what you are asking, so the machine beside you is scoped to the same moment. An AI partner, not a sidebar.
A distributed system has no single instant
So the cut shows its seams, because a scene that hid them would lie at the worst possible moment
What it costs you
- The frozen scene is a constructed cut, not a photograph. Clocks skew, events arrive out of order, ingestion lags, sampling drops some events entirely. Nothing you are looking at happened at exactly the same instant, because in a distributed system there is no such instant.
- Usually the stitch is close enough to be true. In the microsecond races where you most want to stop time, it is not. So the cut shows its seams: a scene that hid its stitching there would lie at the worst possible moment, which is the one moment you cannot afford it.
- Whether it holds at real cardinality is a debt, not a claim. We will publish that with the method in the open, whichever way it lands.
Why we say this out loud: read the manifesto.
Always-On Demo
Running right now, unscripted, and nobody started it for you. It is a synthetic system rather than a customer's, but nothing about it is staged: we point chaos at it and hunt the gap live. Watch for a minute, send it to whoever is on call with you, or scroll on and go play with one yourself.
The Better Way to Monitor and Manage Your Software
Streamlined Setup
Simple integration
Cloud-native and open source friendly
Rapid Root Cause Analysis
Intuitive tooling
Find answers in a single glance. Know the health of your application
AI Powered
AI Assistant by your side
Unlock the power of AI for assistance and resolution
Intuitive Solutions
Conventional and Immersive
Expert tools for every user:
DevOps, SRE, Infra, Education