Tracking Editor
A search-first browser for deciding what gets instrumented. It opens from a Scenario, because Tracking belongs to a recording playbook.
The productive middle¶
Too little Tracking
A Report has little executable story, so behavior becomes hard to explain.
Too much Tracking
The story becomes noise, and every graph turns unreadable.
The Tracking Editor keeps you in the middle: enough call activity to explain behavior, not so much that graphs drown.
How to use it¶
Open a Scenario
Tracking lives inside a Scenario, so start there.
Open the Tracking Editor
Launch it from the Scenario toolbar.
Search and select
Find an assembly, namespace, type, or member, then track the smallest useful surface.
Return and record
Go back to the Scenario and record a clean take.
Track actions¶
Track Everything is a power tool
Use it when you truly need breadth, then immediately plan a second take that trims the noise.
Member inspector¶
Select a member to inspect details and a patchability preview. From here you can also add, enable, disable, or remove a Watch. This is the fastest path from "this property looks suspicious" to a Watch that drives Causal Flow later.
Tracking versus Watches¶
| Concept | Answers | Typical effect |
|---|---|---|
| Tracking | Which execution is captured? | Methods and scopes appear in Report views |
| Watch | Which values are observed? | Value history and causal chains become available |
A common beginner mistake is tracking a type and assuming values are watched automatically. They are related but separate. Configure both when the question is about state change.
Practical strategies¶
Single owner type
Best for "this component's state is wrong."
Boundary plus owner
Best for "something outside sets this."
Public surface first
Best for large types where the full member list is overwhelming.
Harmony and patchability¶
TraceMind uses Harmony-based selective instrumentation under the hood, and the member inspector can preview whether a target is a good patch candidate. If something cannot be tracked usefully, adjust the Scenario instead of forcing a bad capture. Selectivity includes knowing when to choose a different observation point.