Trace
also: traces, traced, execution trace
A step-by-step record of the path one action took through your app, showing each stop along the way and how long it took.
A record of a single operation, such as one web request, as it moves through functions and services, broken into timed steps called spans. Traces show where time went and where a request failed. "Trace" is also a verb: to follow execution through the code.
A package tracking page. Picked up, sorted in Memphis, delayed in Denver, delivered. You see every stop for this one package, and where it got stuck.
Logs tell you what happened across the app. A trace tells the story of one slow or failed action. It's how you find out why checkout takes nine seconds.
I traced the request from the button click to the database. The form sends the date as plain text, and the API reads it as UTC instead of local time, which shifts it back a day.
Trace what happens when a user clicks Publish, step by step, from the button to the database. Tell me where the post's status gets lost.
Mixing up a trace with a stack trace. A stack trace is a snapshot of function calls at one moment of failure. A trace follows one action from start to finish over time.